Skip to main content

​
Overview

CrewForm supports the MCP (Model Context Protocol) — the open standard for connecting AI agents to external tool servers. MCP lets your agents discover and use tools from any MCP-compatible server, expanding their capabilities beyond CrewForm’s built-in tools.
MCP is one of three agentic protocols CrewForm supports, alongside A2A (agent-to-agent) and AG-UI (agent-to-frontend).

​
How It Works

Agent Task  →  Task Runner  →  MCP Client  →  External MCP Server
                                    ↓
                              Tool Discovery
                              Tool Execution
  1. You register MCP servers in Settings → MCP Servers
  2. CrewForm’s task runner connects and discovers available tools
  3. Agents with mcp: tools enabled can call any discovered tool during execution
  4. Tool results flow back into the agent’s reasoning loop

​
Supported Transports

TransportDescriptionUse Case
streamable-httpHTTP-based streaming (default)Cloud-hosted MCP servers
sseServer-Sent EventsReal-time streaming servers
stdioStandard I/OLocal process-based servers

​
Adding an MCP Server

  1. Go to Settings → MCP Servers
  2. Click Add Server
  3. Fill in:
    • Name — Display name (e.g. “GitHub Tools”)
    • URL — Server URL or command (e.g. https://mcp.example.com)
    • Transport — streamable-http, sse, or stdio
    • Config (optional) — JSON object with auth headers, env vars, or command arguments
  4. Click Save — CrewForm discovers and caches available tools

​
Config Examples

HTTP server with auth: 
{
  "headers": {
    "Authorization": "Bearer your-token"
  }
}
stdio server with env vars: 
{
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-github"],
  "env": {
    "GITHUB_TOKEN": "ghp_xxx"
  }
}

​
Enabling MCP Tools on Agents

  1. Open the agent’s configuration
  2. In the Tools section, you’ll see discovered MCP tools listed as mcp:server-name/tool-name
  3. Toggle the tools you want the agent to use
  4. Save — the agent can now use those tools during task execution

​
Tool Discovery

When you add or refresh an MCP server, CrewForm:
  1. Connects to the server using the configured transport
  2. Calls the tools/list method to discover available tools
  3. Caches the tool definitions (name, description, input schema)
  4. Makes them available in the agent configuration UI
Cached tools are refreshed automatically when the server configuration changes. You can also manually refresh from the settings panel.
ServerDescription
@modelcontextprotocol/server-githubGitHub repos, issues, PRs
@modelcontextprotocol/server-filesystemLocal file system access
@modelcontextprotocol/server-postgresPostgreSQL queries
@modelcontextprotocol/server-brave-searchBrave web search
@modelcontextprotocol/server-slackSlack messaging
Browse more at github.com/modelcontextprotocol/servers.

​
Database

MCP servers are stored in the mcp_servers table with workspace-scoped RLS. Each server record includes:
  • Connection config (URL, transport, auth)
  • Cached tool definitions
  • Enabled/disabled status

​
MCP Server Publishing

CrewForm can also act as an MCP Server — exposing your agents as tools that Claude Desktop, Cursor, and other MCP clients can call.

MCP Server Publishing

Learn how to expose your agents as MCP tools for external clients.