MCP Servers

Built-in MCP servers that open your workspace to every AI tool

Every app, workflow, and integration in your Runwork workspace is automatically available via MCP (Model Context Protocol). Connect Claude Desktop, Cursor, Codex, or any MCP-compatible tool and they can read your data, trigger your workflows, call your endpoints, and use your skills. One workspace, every AI tool.

MCP Connections

3 connected

Workspace MCP Server Active

https://acme.runwork.ai/mcp

Connected AI Tools

Claude Desktop Workspace access

Connected

Cursor CRM app only

Connected

Custom AI Agent Workspace access

Connected

Available MCP Tools

query_entity create_entity call_endpoint trigger_workflow trigger_schedule call_integration send_message list_skills +14 more

22 tools available

Capabilities

Workspace MCP Server

One connection point exposes your entire workspace. Every app, entity, workflow, schedule, integration, and skill, all available through a single MCP endpoint.

Per-App MCP Servers

Need focused access? Each app gets its own MCP server URL. Connect Claude to just your CRM, or just your analytics app. Less noise, more precision.

Full Tool Mapping

Everything maps to MCP tools: query entities, call endpoints, trigger workflows, run schedules, use integrations, send channel messages, read skills. Your full workspace as AI tools.

Resources & Prompts

Entity schemas, app manifests, and skill content served as MCP resources and prompts. External AI tools get rich context about your business, not just raw tool calls.

API Key Authentication

Secure access with workspace API keys. Scope keys to specific apps. Create, rotate, and revoke keys from your dashboard. Same security model as your APIs.

Standard Protocol

Streamable HTTP and SSE transports. Works with any tool that speaks MCP. No custom SDKs, no vendor lock-in.

Use Cases

Claude Desktop + your data Cursor with business context Custom AI agents Cross-tool orchestration Automated reporting Data enrichment pipelines

Why It Matters

Your workspace is instantly available to Claude, Cursor, and any MCP client
No setup per tool: connect once, access everything
Per-app servers for granular access control
Open protocol: not locked into any single AI vendor

How It Works

MCP (Model Context Protocol) is the open standard for connecting AI tools to data sources. Runwork gives every workspace a built-in MCP server, so your apps, data, and workflows are accessible to any AI tool that speaks MCP.

The workspace MCP server exposes everything: entities (customers, orders, products), endpoints, workflows, schedules, integrations, components, agents, file storage, channels, and skills. All mapped to MCP tools with proper schemas and descriptions. Connect Claude Desktop and ask it to "query all customers who signed up this month" or "trigger the weekly report workflow."

Per-app MCP servers give more focused access. Each app has its own MCP URL that only exposes that app's capabilities. Connect Cursor to your CRM app and it gets CRM tools without seeing your entire workspace. This is useful for access control and reducing noise in the tool set.

Authentication uses your existing workspace API keys. Keys can be scoped to specific apps for per-app MCP access. The same security model you use for your public APIs applies to MCP connections.

Both Streamable HTTP and SSE (Server-Sent Events) transports are supported. Streamable HTTP works for stateless interactions. SSE handles streaming and long-running operations. Both are MCP standard transports, so any compliant client works out of the box.

MCP also exposes resources (entity schemas, app manifests) and prompts (app skills, channel instructions). External tools don't just get tool calls. They get the full context of your business. The same skills your workspace AI uses internally are available to external tools too.

Frequently Asked Questions

What is MCP (Model Context Protocol)?

MCP is an open standard for connecting AI tools to data sources and capabilities. It defines how AI tools discover available tools, call them, and receive results. Think of it as a universal adapter between AI assistants and your business data. Runwork implements MCP so your workspace is accessible to any compatible AI tool.

Which AI tools work with Runwork MCP?

Any tool that supports the MCP protocol. This includes Claude Desktop, Cursor, Codex, and a growing ecosystem of AI tools. Both Streamable HTTP and SSE transports are supported, so any MCP-compliant client can connect to your Runwork workspace.

What is the difference between workspace and per-app MCP servers?

The workspace MCP server exposes everything across all your apps through one connection. Per-app MCP servers expose only a single app's capabilities. Use workspace MCP when you want broad access, and per-app MCP when you want focused, scoped access. Per-app servers are also useful for sharing a specific app with an external tool without exposing your full workspace.

How do I connect Claude Desktop to my workspace?

Add your workspace MCP server URL and API key to Claude Desktop's MCP configuration. Claude will automatically discover all available tools, resources, and prompts. You can then ask Claude to interact with your workspace data, trigger workflows, and use your app skills. Per-app URLs are also available if you want to connect to a specific app.

Is MCP access secure?

Yes. All MCP connections are authenticated with workspace API keys. Keys can be scoped to specific apps, so you control exactly what each connection can access. You can create, rotate, and revoke keys from your workspace dashboard. The same security model that protects your public APIs applies to MCP connections.

Related Features

APIs Skills Integrations

See How Teams Use MCP Servers

AI Ecosystem CTOs SaaS Teams

Ready to try MCP Servers?

Start vibe-coding with Runwork today.

Get Started Explore More Features