Skip to main content
Glama
@lamatic/mcp
by Lamatic

@lamatic/mcp

npm version npm downloads license node

The unified Model Context Protocol server for Lamatic.ai — manage your org, execute deployed flows, query the docs, and explore AgentKit, all from any MCP-compatible AI agent (Claude, Cursor, Claude Code, and more).

@lamatic/mcp merges four capabilities into a single server so your AI assistant can operate Lamatic end to end:

Prefix

What it does

Package it replaces

dev_*

Manage orgs, projects, flows, contexts & credentials

@lamatic/dev-mcp

graph_*

Execute deployed Lamatic flows

@lamatic/graph-mcp

docs_*

Query Lamatic.ai documentation via RAG

hosted Docs MCP

kit_*

Browse, search & validate AgentKit contributions

—

Each namespace degrades independently — missing credentials for one prefix never break the others.

Requirements

  • Node.js ≥ 18

Related MCP server: mcp-canon

Install

No install needed — run it on demand with npx:

npx @lamatic/mcp

Or install globally to expose the lamatic-mcp binary:

npm install -g @lamatic/mcp
lamatic-mcp

Setup

Claude Desktop / Cursor / Claude Code

Add the server to your MCP config:

{
  "mcpServers": {
    "lamatic": {
      "command": "npx",
      "args": ["-y", "@lamatic/mcp"]
    }
  }
}

Execution-only mode (single flow)

For GraphMCP's execution-only mode (no org key, single flow — e.g. the Studio "Connect with AI" snippet), pass env vars instead:

{
  "mcpServers": {
    "lamatic": {
      "command": "npx",
      "args": ["-y", "@lamatic/mcp"],
      "env": {
        "PROJECT_API_KEY": "<projectApiKey>",
        "PROJECT_ID": "<projectId>",
        "ENDPOINT": "<endpoint>",
        "FLOW_ID": "<flowId>"
      }
    }
  }
}

GitHub token (optional, for AgentKit PR writes)

kit_revalidate_pr posts /validate comments to GitHub. Add a token to raise GitHub's API rate limit and enable comment writes:

{
  "mcpServers": {
    "lamatic": {
      "command": "npx",
      "args": ["-y", "@lamatic/mcp"],
      "env": {
        "GITHUB_TOKEN": "<github-personal-access-token>"
      }
    }
  }
}

Authentication

Prefix

How to authenticate

dev_*

dev_auth_login tool, or LAMATIC_API_KEY + LAMATIC_ORG_ID env vars

graph_*

graph_auth_login (full mode), or PROJECT_API_KEY / PROJECT_ID / ENDPOINT env vars (single-flow)

docs_*

None — proxies to the public hosted endpoint

kit_*

None for read/validate tools; GitHub token (kit_auth_login or GITHUB_TOKEN) only for kit_revalidate_pr

All credentials live in one namespaced file at ~/.lamatic/config.json:

{
  "dev":   { "apiKey": "...", "orgId": "...", "userId": "..." },
  "graph": { "orgApiKey": "...", "projectApiKey": "...", "orgId": "..." },
  "kit":   { "githubToken": "..." }
}

Available tools

dev_* — org, project, flow & credential management

Auth & projects

  • dev_auth_login — Authenticate with Lamatic DevMCP

  • dev_list_projects — List all projects in your organization

  • dev_create_project — Create a new project

  • dev_get_project — Get details of a project

  • dev_update_project — Rename a project

  • dev_delete_project — Delete a project

  • dev_deploy_project — Deploy a project

Flows

  • dev_create_flow — Create a new flow in a project

  • dev_get_flows — List all flows in a project

  • dev_list_all_flows — List all flows for a project

  • dev_update_flow — Update a flow with new nodes and edges

  • dev_rename_flow — Rename a flow

  • dev_update_flow_status — Change a flow's status

  • dev_delete_flow — Delete a flow

Contexts (vector / memory)

  • dev_create_context — Create a new vector or memory context

  • dev_get_context — Get details of a specific context

  • dev_get_all_contexts — List all contexts in a project

  • dev_delete_context — Delete a context

Deployments

  • dev_list_all_deployments — List all deployments for a project

  • dev_get_deployment — Get details of a specific deployment

Models

  • dev_list_model_providers — List available model providers (optionally their models)

  • dev_list_model_creds — List model credentials for a project

  • dev_create_model_creds — Create model credentials for a provider

  • dev_check_model_status — Check the availability status of a model

Integrations & credentials

  • dev_list_supported_integrations — List all supported integrations

  • dev_list_integration_creds — List integration credentials for a project

  • dev_create_integration_creds — Create integration credentials

  • dev_get_cred_info — Get details of a specific credential

  • dev_update_credential — Update an existing credential

  • dev_delete_credential — Delete a credential

  • dev_get_oauth_url — Get an OAuth authorization URL for an integration

graph_* — execute deployed flows

  • graph_auth_login — Authenticate with GraphMCP (only if not configured via env vars)

  • graph_load_project_flows — Load all active flows with their input schemas (org-level access)

  • graph_refresh_flows — Refresh and list all active flows for a project (org-level access)

  • graph_execute_flow — Execute a deployed flow (flowId optional in single-flow mode)

docs_* — documentation Q&A

  • docs_query_docs — Ask any question about Lamatic.ai docs; RAG-powered, no auth required

kit_* — AgentKit browse, search & validation

  • kit_list — List all kits, bundles, and templates in the AgentKit repo

  • kit_get — Get full details for a kit (config, README, flows)

  • kit_search — Search kits by type and/or tag/keyword

  • kit_get_flow — Get the raw .ts source of a flow inside a kit

  • kit_validate_structure — Run CI's Phase 1 structural checks against a local kit before opening a PR

  • kit_check_pr_status — Check Phase 1/Phase 2 validation status and labels on an open PR

  • kit_revalidate_pr — Trigger Phase 2 Studio re-validation by posting the /validate comment (needs GitHub token)

  • kit_auth_login — Store a GitHub token for kit_check_pr_status and kit_revalidate_pr

Architecture notes

  • docs_* does not duplicate the RAG-calling logic from the Lamatic-MCP-Docs repo. It runs a thin MCP client (utils/docsProxy.js) that connects to the hosted endpoint (https://docmcp.lamatic.ai/api/mcp) and forwards the call. The standalone hosted endpoint keeps working unchanged for zero-install users.

  • kit_* reads directly from the public Lamatic/AgentKit GitHub repo via utils/kitProxy.js — there is no hosted Kit API today. If one is ever stood up (the way docs_* proxies to a hosted endpoint), the fetch calls in kitProxy.js are the only thing that needs to change; tool signatures in tools/kit.js stay the same.

  • kit_validate_structure mirrors the Phase 1 checks in validate-pr.yml by hand. There is no CI link between the two files today — if Phase 1's bash logic changes, this needs a matching manual update or the two will silently disagree on what counts as a valid kit.

Local development

git clone https://github.com/Lamatic/Lamatic-MCP.git
cd lamatic-mcp
npm install
node server.js

Windows setup

npx -y @lamatic/mcp won't work on Windows because npx can't determine the executable. Use the local path approach instead:

  1. Clone the repo:

git clone https://github.com/Lamatic/Lamatic-MCP.git
cd Lamatic-MCP
npm install
  1. Add to your claude.json or claude_desktop_config.json:

"lamatic": {
  "type": "stdio",
  "command": "node",
  "args": ["C:/path/to/Lamatic-MCP/server.js"],
  "env": {}
}

Mac/Linux users can use npx directly:

"lamatic": {
  "type": "stdio",
  "command": "npx",
  "args": ["-y", "@lamatic/mcp"],
  "env": {}
}

Available Tools

44 tools
dev_auth_loginC

Authenticate with Lamatic DevMCP

Inputs: orgId (required), apiKey (required), userId (required).

dev_check_model_statusC

Check the availability status of a specific model

Inputs: modelName (required), projectId (required).

dev_create_contextB

Create a new context (vector or memory) in a Lamatic project

Inputs: name (required), type (required), projectId (required).

dev_create_flowC

Create a new flow in a Lamatic project

Inputs: name (required), projectId (required).

dev_create_integration_credsB

Create new integration credentials for a Lamatic project

Inputs: name (required), projectId (required), credentials (required), integration (required).

dev_create_model_credsB

Create new model credentials for a provider in a Lamatic project

Inputs: name (required), provider (required), projectId (required), credentials (required).

dev_create_projectC

Create a new Lamatic project

Inputs: name (required), region (required).

dev_delete_contextC

Delete a context from a Lamatic project

Inputs: contextId (required), projectId (required).

dev_delete_credentialB

Delete a credential from a Lamatic project

Inputs: projectId (required), credentialId (required).

dev_delete_flowB

Delete a flow from a Lamatic project

Inputs: flowId (required), projectId (required).

dev_delete_projectC

Delete a Lamatic project

Inputs: projectId (required).

dev_deploy_projectC

Deploy a Lamatic project

Inputs: projectId (required), name, description.

dev_get_all_contextsA

List all contexts in a Lamatic project

Inputs: projectId (required).

dev_get_contextB

Get details of a specific context in a Lamatic project

Inputs: contextId (required), projectId (required).

dev_get_cred_infoA

Get details of a specific credential in a Lamatic project

Inputs: projectId (required), credentialId (required).

dev_get_deploymentA

Get details of a specific deployment in a Lamatic project

Inputs: projectId (required), deploymentId (required).

dev_get_flowsC

List all flows in a Lamatic project

Inputs: projectId (required).

dev_get_oauth_urlC

Get an OAuth authorization URL for an integration in a Lamatic project

Inputs: nodeName (required), projectId (required), redirectUri (required), credentialName (required).

dev_get_projectB

Get details of a Lamatic project

Inputs: projectId (required).

dev_list_all_deploymentsA

List all deployments for a Lamatic project

Inputs: projectId (required).

dev_list_all_flowsC

List all flows for a Lamatic project

Inputs: projectId (required).

dev_list_integration_credsC

List all integration credentials for a Lamatic project

Inputs: projectId (required).

dev_list_model_credsB

List all model credentials for a Lamatic project

Inputs: projectId (required).

dev_list_model_providersB

List all available model providers, optionally including their models

Inputs: projectId (required), includeModels.

dev_list_projectsA

List all projects in your Lamatic organization

Inputs: no named parameters.

dev_list_supported_integrationsB

List all supported integrations available for a Lamatic project

Inputs: projectId (required).

dev_rename_flowB

Rename a flow in a Lamatic project

Inputs: name (required), flowId (required), projectId (required).

dev_update_credentialB

Update an existing credential in a Lamatic project

Inputs: projectId (required), credentials (required), credentialId (required).

dev_update_flowC

Update an existing Lamatic flow with new nodes and edges

Inputs: edges (required), nodes (required), flowId (required), projectId (required), +1 more.

dev_update_flow_statusB

Update the status of a flow in a Lamatic project

Inputs: flowId (required), status (required), projectId (required).

dev_update_projectC

Rename a Lamatic project

Inputs: name (required), projectId (required).

docs_query_docsA

Ask any question about Lamatic.ai documentation. Uses RAG to search across all indexed docs and return a precise answer. No authentication required.

Inputs: text (required).

graph_auth_loginA

Authenticate with Lamatic GraphMCP (only needed if not already configured via environment variables)

Inputs: projectApiKey (required), orgId, orgApiKey.

graph_execute_flowB

Execute a deployed Lamatic flow. If connected via a single-flow integration, flowId can be omitted.

Inputs: payload (required), flowId, projectId.

graph_load_project_flowsB

Load all active flows for a project with their input schemas (requires org-level access)

Inputs: projectId (required).

graph_refresh_flowsB

Refresh and list all active flows for a project (requires org-level access)

Inputs: projectId (required).

kit_auth_loginA

Store a GitHub personal access token for kit_check_pr_status and kit_revalidate_pr. Token needs public_repo scope (or repo scope for private orgs).

Inputs: githubToken (required).

kit_check_pr_statusA

Check the Phase 1 (structural) and Phase 2 (Studio runtime) validation status and labels on an open AgentKit PR. Requires a GitHub token (kit_auth_login or GITHUB_TOKEN env var) for higher rate limits, but works without one for public PRs at GitHub's unauthenticated rate limit.

Inputs: prNumber (required).

kit_getA

Get full details for a single kit — its lamatic.config.ts, README, and list of flows. No authentication required.

Inputs: name (required).

kit_get_flowA

Get the raw .ts source of a specific flow inside a kit. No authentication required.

Inputs: kitName (required), flowName (required).

kit_listA

List all kits, bundles, and templates available in the Lamatic AgentKit repository. No authentication required.

Inputs: no named parameters.

kit_revalidate_prA

Trigger a Phase 2 Studio re-validation on an open AgentKit PR by posting the /validate comment. Requires a GitHub token with comment-write access (kit_auth_login or GITHUB_TOKEN env var).

Inputs: prNumber (required).

kit_validate_structureA

Run the same Phase 1 structural checks used in CI (validate-pr.yml) against a local kit folder, before opening a PR. No authentication required.

Inputs: kitPath (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 44 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is direct overlap between dev_get_flows and dev_list_all_flows, which both list flows. The three auth_login tools are also similar in name though they authenticate different contexts.

    Naming Consistency4/5

    Tools consistently use prefix_category + verb_noun in snake_case. However, the duplicate dev_get_flows and dev_list_all_flows break the naming pattern, and some verbs are inconsistent (e.g., 'get' vs 'list' for similar operations).

    Tool Count2/5

    44 tools is excessive for a single MCP server, covering too many subdomains (dev, docs, graph, kit). This high count suggests the server could be split into smaller, more focused servers.

    Completeness4/5

    The tool surface covers most CRUD operations for projects, flows, contexts, credentials, and deployments. Minor gaps exist, such as missing update for contexts and delete for deployments, but overall it is fairly complete for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers