For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform Keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily Executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a Product
    • Setting up a Chat Surface
    • Setting up an API Surface
    • Setting up an MCP Surface
    • Setting up an A2A Surface
    • Setting up a Slack Surface
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
  • Evals
    • What are Evals?
    • Running an Eval
  • Schedules
    • What are Schedules?
  • Logs
    • What are Logs?
  • Integrations
    • Connecting AI model providers
  • Settings
    • What's in Settings?
    • Available AI models
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
Dashboard
LogoLogo
On this page
  • What is MCP?
  • Create an MCP Surface
  • Configure tools
  • Connect your AI IDE
  • Connect to Claude Desktop
  • With OAuth
  • With API Key
  • Connect to Cursor
  • With OAuth
  • With API Key
  • Manage your Surface
  • Overview
  • Endpoints
  • Keys
  • Ship
  • Verify your setup
  • Next steps
Products & Surfaces

Setting Up an MCP Surface

Was this page helpful?
Previous

Setting Up an A2A Surface

Next
Built with

An MCP (Model Context Protocol) Surface turns your Runtype Capabilities into tools that AI assistants can discover and use directly. Once connected, AI IDEs like Claude Desktop, Cursor, and VS Code can call your Flows and Agents on demand from the chat interface.

What is MCP?

MCP is an open protocol that lets AI assistants interact with external tools and services. When you create an MCP Surface, your Product’s Capabilities are automatically published as tools that any MCP-compatible client can discover and invoke.

This enables workflows like:

  • Claude Desktop calling your data retrieval Flow during analysis
  • Cursor invoking your code generation Agent in a coding session
  • VS Code using your custom tools through the Cline extension or GitHub Copilot

Your Product needs at least one Capability to expose as a tool. If you have not added one yet, create a Flow or Agent first. When you create an MCP Surface from the launch panel, the first Capability is added automatically.

Create an MCP Surface

  1. Open your Product.
  2. Find the Surfaces section.
  3. Click Add Surface.
  4. Select MCP Server.
  5. Configure the Surface.
  6. Click Create.

A setup wizard walks you through choosing which Capabilities to expose as tools and connecting to your AI IDE.

Configure tools

Choose which Capabilities to expose as MCP tools. Each Capability attached to your Product appears with an enable or disable toggle. Use Enable All or Disable All to update everything at once.

You can change which tools are enabled later from the Surface’s Endpoints tab.

Connect your AI IDE

The Ship step helps you connect your Surface to an AI IDE. Start by choosing an authentication mode:

  • OAuth — Recommended for Claude Desktop and Cursor. Paste the MCP server URL into your IDE and complete authentication in the browser.
  • API Key — Use a Bearer token for clients that do not support OAuth or when you want key-based access.
  • Public — No authentication required. Use this for public tools or quick testing.

Connect to Claude Desktop

Use one of these setup methods in the Ship tab.

With OAuth

  1. Open Claude Desktop.
  2. Go to Settings → Developer → Edit Config.
  3. Add the MCP server URL from the Ship tab to mcpServers.
  4. Restart Claude Desktop.
  5. Authorize in the browser prompt.

With API Key

  1. Open Claude Desktop.
  2. Go to Settings → Developer → Edit Config.
  3. Add the provided config to mcpServers.
  4. Replace YOUR_API_KEY with an API key.
  5. Restart Claude Desktop.

Config file location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Connect to Cursor

Use one of these setup methods in Cursor settings.

With OAuth

  1. Open Cursor.
  2. Go to Settings with Cmd/Ctrl + ,.
  3. Search for MCP.
  4. Click Add new MCP server.
  5. Paste the MCP server URL.
  6. Authorize in the browser prompt.

With API Key

  1. Open Cursor.
  2. Go to Settings with Cmd/Ctrl + ,.
  3. Search for MCP.
  4. Click Add new MCP server.
  5. Paste the provided config.
  6. Replace YOUR_API_KEY with an API key.
  7. Reload the window.

Manage your Surface

Overview

The Overview tab shows your Surface name, status, and key details. Make sure the Surface status is Active before you connect AI IDEs.

Endpoints

The Endpoints tab shows your MCP endpoint URL and lets you enable or disable individual Capabilities as tools.

You can also override a Capability name or description for this Surface. This is useful when the same Capability is used across multiple Surfaces with different contexts.

For programmatic integrations, the Advanced: Programmatic Integration section provides these endpoints:

  • MCP Server URL: https://api.runtype.com/v1/products/{productId}/surfaces/{surfaceId}/mcp
  • MCP Manifest: https://api.runtype.com/v1/products/{productId}/surfaces/{surfaceId}/mcp/.well-known/mcp.json

Keys

MCP Surfaces can use API keys for authentication. Create and manage keys in the Keys tab.

To create an API key:

  1. Go to the Keys tab.
  2. Click Generate API Key.
  3. Configure the key.
  4. Click Generate.
  5. Copy and store the key securely.

Production keys are hashed and cannot be recovered after creation. Generate a new key if one is lost. Test keys can be revealed later from the Keys tab.

The Ship tab can create a default test key for quick setup, so you do not need to create one manually to get started. Store API keys securely and never commit them to version control. Rotate keys immediately if they are exposed.

Ship

The Ship tab provides configuration snippets for Claude Desktop, Cursor, and other MCP-compatible clients. You can return to this tab anytime to copy connection details or create a quick-start key.

Verify your setup

After you connect an AI IDE, confirm your Capabilities appear as available tools:

  • Claude Desktop: Look for the tools icon in the chat interface.
  • Cursor: Check the MCP section in the chat panel.
  • VS Code (Cline): Open the Cline sidebar settings to view available tools.

Try asking the AI assistant to use one of your Capabilities by name. It should appear as an available tool and run when invoked.

If tools are not appearing, check that your Product status is Active and that the Capabilities you want are enabled in the Endpoints tab.

Next steps

  • What are Surfaces? if you want a broader overview of Surface types
  • What are Products? if you want to understand how Products, Capabilities, and Surfaces fit together
  • Quickstart: From Flow to Live Surface for a full build-and-deploy walkthrough
  • Creating a Product if you need to set up the Product first