MartechDB
MartechDB
Toggle sidebar

Lamatic.ai MCP server

lamatic.ai

Yes. Lamatic.ai publishes an official MCP server at https://mcp.lamatic.ai/mcp. It's hosted. It offers 34 tools. We last checked it on 22 Nov 2026.

Official MCP server
Hosted
Sign-in: see vendor docs

Official: answers MCP requests at mcp.lamatic.ai, on Lamatic.ai's own domain lamatic.ai. Checked 22 Nov 2026. Maintained by Stuart Brameld.

Key facts

As of 22 Nov 2026, Lamatic.ai's official MCP server scores 55/100 (provisional) on MartechDB's Agent Readiness Index (v1.1). It answered 55 of our 55 checks in the last 90 days and lists 34 tools.

How the Agent Readiness Index works · Wrong? Suggest a correction

Lamatic.ai MCP server review

55/100

Lamatic.ai's MCP server scores 55/100 on MartechDB's Agent Readiness Index: usable by AI agents, with gaps.

The good

  • Hosted by Lamatic.ai: connect by URL, with nothing to install

  • Answered 100% of our checks in the last 90 days

The bad

  • Nothing we've found.

Not checked yet: how you sign in; a docs page listing its tools; what agent access costs. Anything not checked scores nothing.

Official MCP server

Lamatic.ai MCP server

Address
https://mcp.lamatic.ai/mcp
Runs
Hosted
Sign-in
Sign-in: see vendor docs
Official MCP Registry
Not listed
How we know it's official
  • Answers MCP requests at mcp.lamatic.ai, on Lamatic.ai's own domain lamatic.ai.
Checked 22 Nov 2026.
Tools
34 tools · listed 26 Oct 2026
First seen
1 Oct 2026
Last checked
Reachable ·
16 Nov 2026: reachable
17 Nov 2026: reachable
18 Nov 2026: reachable
19 Nov 2026: reachable
20 Nov 2026: reachable
21 Nov 2026: reachable
22 Nov 2026: reachable
Uptime
100% · 55 of 55 checks reachable since 1 Oct 2026

Lamatic.ai MCP server tools (34)

As the server lists them. Names and descriptions are the vendor's own.

  • graph_authenticate Sign in with a token

    Store a Lamatic personal access token for this connection, so the other tools can act on the user's project. Call this ONLY with a token the user has just given you. Never invent one, never reuse a token from earlier in the conversation without being asked, and never call this to "try" a value — a wrong token is rejected, not retried. If the user has no token: send them to https://studio.lamatic.ai/pat/new, where they pick the project and the permissions the token may use, then paste the result back to you. The token identifies its own project, so there is nothing else to ask them for. On success this reports the project, the role, and which tools are now usable. The token is validated before it is stored, so a failure here means the token itself is bad — relay the reason rather than retrying.

  • graph_auth_status Check token access
    Read-only

    Diagnostic tool: reports which project this token owns, the role it was minted under, and exactly which tools it can and cannot use — without ever returning the token itself. Call this FIRST whenever another tool fails with an authentication or permission error, and BEFORE asking the user for any configuration: the only thing a user supplies is the personal access token itself, and everything else (project, organization, role, scopes) is read back from the token itself. The "cannot use" list is the important part — a scope a token does not carry will never work, so do not retry those tools; the user must mint a new token. Takes no arguments.

  • graph_get_guide Read a Lamatic guide
    Read-only

    Read a Lamatic reference guide. Unlike MCP resources — which many clients only expose for a user to attach — this is readable by you directly, at any point. Call it when: you are about to build or edit a flow (topic 'conventions', plus 'flow-template-chat' for a working starting point); a flow fails with an unhelpful message or a deployment succeeds without changing anything (topic 'troubleshooting'); or you need to know whether something is possible before promising it (topic 'capabilities'). Topics: 'capabilities' — scope, lifecycle, rate limits, token expiry, what is out of scope. 'conventions' — the four rules for a flow that actually runs, including the node_type vs definition_key trap. 'troubleshooting' — ranked triage for failures. 'flow-template-chat' — a verified three-node chat flow as copyable JSON.

  • graph_list_nodes List node types
    Read-only

    List every node TYPE available for building Lamatic flows — the building blocks (triggers, LLM calls, integrations, logic, etc.), not flow instances. Each entry gives a definition key, node type, label, and builder guidance. CRITICAL — the two fields have different jobs. `node_type` is what goes in a flow node's data.nodeId; `definitionKey` is ONLY the argument graph_get_node takes. They differ for variant rows such as triggers, which are keyed <node_type>_trigger (definitionKey "chatTriggerNode_trigger", node_type "chatTriggerNode"), while standalone and response nodes have them identical ("LLMNode", "chatResponseNode"). Put the bare node_type in data.nodeId; a suffixed definitionKey there matches no executor at runtime, so the node silently pass-throughs its input and does nothing — no error, no log entry, the flow just returns the wrong thing. Whether a node is a trigger is carried by the flow node's top-level `type` ("triggerNode"), not by its nodeId. Paginated (default 50, max 20…

  • graph_get_node Read a node definition
    Read-only

    Get one node TYPE's full definition JSON: its configuration fields, their types, defaults, and validation rules. This is the schema for a single node in a flow's `nodes` array — call it once per distinct node type you're about to include, before graph_create_flow or graph_update_flow, so the node's `data` object is shaped correctly instead of guessed. A 404 here means the key does not exist: re-check graph_list_nodes rather than proceeding, because a bad key produces a flow that deploys successfully and then fails at runtime.

  • graph_load_flow_details Read a flow
    Read-only

    Load one specific flow's full definition: its complete node/edge graph, its trigger node and trigger type, and its input schema (parsed from the trigger's advance_schema, same as what graph_list_flows shows). Use this when you already know the flowId (from the user, or a prior graph_list_flows call) and need just that flow's details — for browsing/searching across all flows by name, use graph_list_flows instead, which returns the same schema info for every active flow in one call.

  • graph_create_flow Create a flow

    Create a NEW Lamatic flow from a node/edge graph you assemble (this cannot edit an existing flow — use graph_update_flow for that). REQUIRED procedure — do not skip steps 1-2, they prevent the two failures that silently break flows: 1. graph_list_nodes — find the nodes you need; copy each one's `definition_key` (the argument for graph_get_node) AND its `node_type` (the value that goes in data.nodeId). 2. graph_get_node for each distinct key — get its real config shape and its `node_template`. 3. graph_list_models — if any node calls a model, ASK THE USER which model and credential to use before continuing. Do not pick one yourself, even if only one credential exists. 4. Build nodes/edges, then call this tool. 5. graph_trigger_deployment — a created flow does NOT run until deployed. TWO MISTAKES THAT PRODUCE A FLOW THAT SAVES, VALIDATES, AND DEPLOYS SUCCESSFULLY, THEN MISBEHAVES AT RUNTIME: (a) Using a registry definition_key as data.nodeId instead of the bare node_type. data.nodeId mu…

  • graph_update_flow Replace a flow graph
    Can delete or overwrite

    Edit an EXISTING flow in place (same flowId), unlike graph_create_flow which always makes a new one. FULL REPLACEMENT, NOT A PATCH: whatever you pass as `nodes`/`edges` becomes the flow's entire graph. Anything you omit is deleted. So for any change short of a total rewrite: (1) graph_load_flow_details to fetch the current graph, (2) edit that array, keeping everything you are not changing, (3) pass the complete result here. Passing only the nodes you touched will silently delete the rest of the flow. The same two silent-failure traps as graph_create_flow apply to any node you add or modify: (a) data.nodeId must be the bare `node_type` from graph_list_nodes ("chatTriggerNode", "LLMNode", "chatResponseNode"), NOT the registry `definition_key` with its "_trigger" / "_action_…" suffix — that key is only the argument to graph_get_node. A suffixed nodeId matches no executor and the node silently pass-throughs its input at runtime, with no error and no log entry. (b) model nodes need a real…

  • graph_execute_flow Run a flow

    Run a deployed Lamatic flow synchronously with an input payload and return its status and result. Before calling this, know the flow's input schema — get it from graph_list_flows or graph_load_flow_details — and build `payload` with exactly those keys; extra or missing required keys are the most common cause of a validation error or an empty/wrong result. If the flow has no input schema, pass an empty object. A non-success execution status is returned as a tool error (not a silent success) with the result payload attached, so you can see and explain why it failed. flowId is required — this server is not pinned to one flow. If this returns a bare "Workflow execution failed" with no detail, the usual causes are, in order: (1) the flow was never deployed after being created or edited — run graph_trigger_deployment; (2) a node's data.nodeId is a registry definition_key rather than the bare node_type (check against graph_list_nodes — a suffixed nodeId makes that node silently do nothing in…

  • graph_list_flows List flows
    Read-only

    List every ACTIVE flow in the project (inactive/draft flows are excluded), each with its description, tags (if set in Studio), trigger type, and its full input schema — the starting point for "what flows can I run" or "run the X flow" style requests, and for grouping flows by topic without guessing from the name alone. Each flow is tagged either ✅ Manually executable (safe to call directly via graph_execute_flow) or ⚠️ Not manually executable (it only fires from a real trigger event — e.g. a Cron schedule or a Google Sheets row — and calling it here with a fabricated payload will likely fail or do nothing useful; tell the user this instead of forcing it). Always call this (or graph_load_flow_details if the flowId is already known) before graph_execute_flow to confirm the flow exists and get its exact input field names.

Connect your AI to Lamatic.ai

Add the official Lamatic.ai MCP server to Claude, ChatGPT or your editor.

Connect Lamatic.ai MCP to Claude

Claude.ai and Claude Desktop

  1. Open Customize, then Connectors.

  2. Click +, then Add custom connector.

  3. Name it Lamatic.ai, paste the address below and click Add.

Claude Code

Lamatic.ai MCP server questions

Does Lamatic.ai have an official MCP server?

Yes. Lamatic.ai publishes its MCP server itself. Its address is on Lamatic.ai's own domain (mcp.lamatic.ai). MartechDB only lists servers a vendor publishes, never community copies.

What is the Lamatic.ai MCP server URL?

The address is https://mcp.lamatic.ai/mcp.

How do I connect Lamatic.ai MCP to Claude, ChatGPT or Cursor?

In Claude, add https://mcp.lamatic.ai/mcp as a custom connector (Customize, Connectors, Add custom connector). In Cursor, use the Add to Cursor link on MartechDB's page, or paste the JSON settings into your mcp.json. In Claude Code, run: claude mcp add --transport http lamaticai https://mcp.lamatic.ai/mcp

What can the Lamatic.ai MCP server do?

It offers 34 tools, including graph_authenticate, graph_auth_status, graph_get_guide, graph_list_nodes and graph_get_node (as listed on 26 Oct 2026). 19 are marked read-only and 5 can delete or overwrite data.

Is the Lamatic.ai MCP server in the official MCP Registry?

No. Lamatic.ai hasn't published it to the official MCP Registry.

Is the Lamatic.ai MCP server working?

Yes. It answered our most recent check. We last checked it on 22 Nov 2026.

What are the alternatives to Lamatic.ai's MCP server?

In Data integration, the most agent-friendly alternatives with an official MCP server are Needle (97/100), Supermetrics (97/100), Activepieces (97/100), IFTTT (92/100) and import.io (92/100). Lamatic.ai scores 55/100 on the same index.

Alternatives to Lamatic.ai's MCP server

Vendors in Data integration with an official MCP server, the most agent-friendly first. Lamatic.ai scores 55/100.

Compare all 52 Data integration vendors →

Use with AI

Connect your AI to MartechDB

Then ask it about Lamatic.ai, or any of the 1,850 marketing tools with an official MCP server. Free, no sign-in.

Claude.ai and Claude Desktop

  1. Open Customize, then Connectors.

  2. Click +, then Add custom connector.

  3. Name it MartechDB, paste the address below and click Add. There's no sign-in.

The free plan allows one custom connector. On Team and Enterprise plans, an owner adds the connector first.

Show that your MCP server is verified

If you work at Lamatic.ai, add this badge to your MCP docs or README. It's free, it's the same for every vendor, and it updates from our daily checks: it shows uptime while the server responds, and says so if it stops.

Official MCP server, verified by MartechDB
HTML
Markdown

Something wrong or out of date? Suggest a correction or email us, and we'll check it against the evidence. Every correction we make is listed on Corrections.