AI Protocol (MCP)

​

Before you start

• Your project needs a release. MCP always runs the latest release — changes you make in the editor afterwards don’t reach your AI clients until you release again.
• Only public Blueprints appear as tools.
• You need an API key.

​

Get the endpoint URL

1. Open your Blueprint in the editor.
2. Click the Share button in the toolbar.
3. Select Connect.
4. In the Connect dialog, select the AI Protocol (MCP) tab.

​

Standard Endpoint

https://lab.leapter.com/runtime/api/v1/{appspace}/{project-id}/mcp

​

Real-Time Streaming Endpoint (SSE)

https://lab.leapter.com/runtime/api/v1/{appspace}/{project-id}/mcp/sse

​

Authentication

• Header name: X-API-Key
• Header value: your API key

​

Connect with Claude Desktop

1. Copy the Standard Endpoint URL from the Connect dialog.
2. Open Claude Desktop and go to Settings → Developer → Edit Config.
3. Add an MCP server entry in your claude_desktop_config.json:

{
  "mcpServers": {
    "leapter": {
      "url": "https://lab.leapter.com/runtime/api/v1/{appspace}/{project-id}/mcp",
      "headers": {
        "X-API-Key": "your-api-key"
      }
    }
  }
}

4. Replace {appspace}, {project-id}, and your-api-key with your actual values.
5. Restart Claude Desktop.

​

Connect with Cursor

1. Copy the Standard Endpoint URL from the Connect dialog.
2. In Cursor, open Settings → MCP.
3. Add a new MCP server with:
   • URL: your Standard Endpoint
   • Headers: X-API-Key: your-api-key
4. Save and your public Blueprints become available as tools in Cursor’s AI features.

​

Connect with other MCP clients

• The Standard Endpoint or SSE Streaming Endpoint URL (depending on what the client supports)
• An API key passed as the X-API-Key header

​

What to do next

• Web API (OpenAPI) — call your Blueprints through a REST API instead
• API Keys — create and manage API keys
• MCP Agent Workflow — use your Blueprints as tools in an n8n AI agent