@lamatic/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOW_ID | No | Flow ID for graph execution-only mode | |
| ENDPOINT | No | Endpoint for graph execution-only mode | |
| PROJECT_ID | No | Project ID for graph execution-only mode | |
| GITHUB_TOKEN | No | GitHub token for kit_revalidate_pr tool (optional) | |
| LAMATIC_ORG_ID | No | Organization ID for dev_* tools (used with LAMATIC_API_KEY) | |
| LAMATIC_API_KEY | No | API key for dev_* tools (alternative to dev_auth_login) | |
| PROJECT_API_KEY | No | Project API key for graph execution-only mode |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dev_auth_loginC | Authenticate with Lamatic DevMCP |
| dev_create_projectC | Create a new Lamatic project |
| dev_get_projectB | Get details of a Lamatic project |
| dev_create_flowC | Create a new flow in a Lamatic project |
| dev_get_flowsC | List all flows in a Lamatic project |
| dev_deploy_projectC | Deploy a Lamatic project |
| dev_list_projectsA | List all projects in your Lamatic organization |
| dev_update_projectC | Rename a Lamatic project |
| dev_delete_projectC | Delete a Lamatic project |
| dev_update_flowC | Update an existing Lamatic flow with new nodes and edges |
| dev_delete_flowB | Delete a flow from a Lamatic project |
| dev_list_all_flowsC | List all flows for a Lamatic project |
| dev_rename_flowB | Rename a flow in a Lamatic project |
| dev_update_flow_statusB | Update the status of a flow in a Lamatic project |
| dev_create_contextB | Create a new context (vector or memory) in a Lamatic project |
| dev_delete_contextC | Delete a context from a Lamatic project |
| dev_get_contextB | Get details of a specific context in a Lamatic project |
| dev_get_all_contextsA | List all contexts in a Lamatic project |
| dev_list_all_deploymentsA | List all deployments for a Lamatic project |
| dev_get_deploymentA | Get details of a specific deployment in a Lamatic project |
| dev_list_model_credsB | List all model credentials for a Lamatic project |
| dev_list_model_providersB | List all available model providers, optionally including their models |
| dev_check_model_statusC | Check the availability status of a specific model |
| dev_create_model_credsB | Create new model credentials for a provider in a Lamatic project |
| dev_list_supported_integrationsB | List all supported integrations available for a Lamatic project |
| dev_list_integration_credsC | List all integration credentials for a Lamatic project |
| dev_create_integration_credsB | Create new integration credentials for a Lamatic project |
| dev_get_cred_infoA | Get details of a specific credential in a Lamatic project |
| dev_get_oauth_urlC | Get an OAuth authorization URL for an integration in a Lamatic project |
| dev_delete_credentialB | Delete a credential from a Lamatic project |
| dev_update_credentialB | Update an existing credential in a Lamatic project |
| graph_auth_loginA | Authenticate with Lamatic GraphMCP (only needed if not already configured via environment variables) |
| graph_load_project_flowsB | Load all active flows for a project with their input schemas (requires org-level access) |
| graph_execute_flowB | Execute a deployed Lamatic flow. If connected via a single-flow integration, flowId can be omitted. |
| graph_refresh_flowsB | Refresh and list all active flows for a project (requires org-level access) |
| 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. |
| kit_listA | List all kits, bundles, and templates available in the Lamatic AgentKit repository. No authentication required. |
| kit_getA | Get full details for a single kit — its lamatic.config.ts, README, and list of flows. No authentication required. |
| kit_searchA | Search kits by type (kit/bundle/template) and/or tag/keyword. No authentication required. |
| kit_get_flowA | Get the raw .ts source of a specific flow inside a kit. No authentication 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. |
| 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. |
| 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). |
| 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). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 44 tools
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.
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).
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.
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.