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
    • MCP authentication
    • Authenticating with product API keys
    • Embedding the chat widget (script tag)
    • Embedding the chat widget (React)
    • Surface orchestration modes
    • Product views
    • Adding Capabilities to a product
    • Connecting external agents
    • How A2A works
    • Connecting to Cursor / VS Code
    • Connecting to Claude Desktop
    • Scoping API keys to capabilities
    • Auto-generated OpenAPI spec
    • Calling your API endpoints
    • Client tokens and domain restrictions
    • AI-powered theme generation
    • Widget theming and customization
    • Product versioning and status
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
    • Using prompt steps
    • Using transform-data steps
    • Using conditional steps
    • Using fetch-url and api-call steps
    • Using record steps (upsert/retrieve)
    • Flow variables and templates
    • Flow versioning and publishing
    • Running flows in batch
    • Handling batch failures
    • Debugging flows
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
    • Using records in flows
    • Filtering and searching records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
    • Runtime tools
  • Evals
    • What are Evals?
    • Running an Eval
    • Interpreting eval results
  • Schedules
    • What are Schedules?
    • Automating batch processing
  • Logs
    • What are Logs?
    • Working with Logs
  • Integrations
    • Connecting AI model providers
    • Slack integration
    • Google Workspace integration
    • GitHub integration
    • Linear integration
    • Weaviate (vector search)
    • Firecrawl (web scraping)
    • Exa (web search)
  • Settings
    • What's in Settings?
    • Available AI models
    • What are Organizations?
    • Managing AI models
    • Managing API keys
    • Billing and plans
    • Usage data
    • Team members and permissions
    • Appearance and preferences
    • Integrations (PostHog, Weaviate, Daytona)
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
    • Flow execution failures
    • Common errors and solutions
    • Authentication issues
Dashboard
LogoLogo
On this page
  • Prerequisites
  • For Cursor
  • With OAuth (recommended)
  • With API Key
  • For VS Code with Cline
  • Open Cline settings
  • Add your server
  • Reload Cline
  • Verify connection
  • Using your Capabilities
  • Troubleshooting
  • Next steps
Products & Surfaces

Connecting to Cursor / VS Code

Was this page helpful?
Previous

Connecting to Claude Desktop

Next
Built with

Connect your Runtype MCP Surface to Cursor or VS Code to give your AI coding assistant access to your Capabilities.

Prerequisites

  • Cursor or VS Code installed
  • An active MCP Surface in Runtype
  • MCP server URL from your Surface settings (found in the Ship tab)

For Cursor

With OAuth (recommended)

  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 from the Ship tab.
  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 from the Ship tab.
  6. Replace YOUR_API_KEY with an MCP API key (with the mcp_ prefix) from the Keys tab.
  7. Reload the window.

For VS Code with Cline

Open Cline settings

  1. Open VS Code
  2. Click the Cline icon in the sidebar
  3. Click the gear icon (Settings)
  4. Scroll to MCP Servers
  5. Click Edit MCP Settings

Add your server

Paste the MCP server URL from the Ship tab. If using API key authentication, add the key with the mcp_ prefix.

Reload Cline

  1. Save the configuration
  2. Close and reopen the Cline sidebar

Verify connection

Check that your tools are available:

  1. Open the AI assistant chat
  2. Look for tools/MCP indicator
  3. Your Runtype Capabilities should be listed as available tools

Using your Capabilities

The AI assistant will automatically use your tools when appropriate. You can also explicitly request them:

“Use the code-review tool to analyze this file”

The assistant invokes your Runtype Capability and incorporates the results into its response.

MCP tools work best when they are focused and well-described. A tool that “gets customer data” is clearer to the AI than a generic “database query” tool.

Troubleshooting

Server fails to connect:

  • Verify your API key is valid and uses the mcp_ prefix
  • Check that the MCP Surface status is Active in Runtype
  • Look for errors in the IDE’s output panel

Tools not visible:

  • Check that your Product has active Capabilities
  • Verify Capabilities are enabled in the Endpoints tab of your MCP Surface
  • Reload the IDE window

Next steps

  • Connecting to Claude Desktop for Claude integration
  • MCP authentication for security details
  • Setting up an MCP Surface