LanguageEN
Home
Docs
Reference / MCP Integrations

MCP Integrations

Heddle can act as a Model Context Protocol host, so agents can use ecosystem tools such as Notion, Anytype, GitHub, and other MCP servers without bespoke Heddle integrations.

How MCP works in Heddle

MCP support is workspace-scoped and operator-controlled. You configure servers, explicitly enable the ones Heddle may connect to, refresh their tool catalog, and then future agent turns can see the cached MCP tools.

Configuration is not permission. Saving an MCP server config does not enable it, does not refresh its tools, and does not grant unattended execution. Tool calls still flow through Heddle approvals and traces.

Basic flow

1. Paste or edit a standard MCP settings JSON document.
2. Enable one configured server for the workspace.
3. Refresh the server so Heddle can cache its current tool catalog.
4. Let the agent inspect and call cached MCP tools through Heddle's normal tool path.

Configure servers

Use the common mcpServers JSON shape. In the browser control plane, open Settings -> MCP and paste the full JSON document into the Configuration editor. In terminal chat, run /mcp config to open .heddle/mcp.json in your normal editor.

{
  "mcpServers": {
    "notion": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "notion-mcp-server"],
      "env": {
        "NOTION_TOKEN": "${env:NOTION_TOKEN}"
      }
    },
    "anytype": {
      "type": "http",
      "url": "https://example.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:ANYTYPE_TOKEN}"
      }
    }
  }
}

Commands

Slash commands manage the same workspace MCP state used by the browser settings page.

/mcp
/mcp config
/mcp enable notion
/mcp refresh notion
/mcp disable notion

What the agent sees

After a server is enabled and refreshed, Heddle exposes a small MCP broker plus cached namespaced tools.

mcp_list_tools

Lists enabled servers and cached MCP tools.

mcp_call_tool

Approval-gated broker call for an enabled server and tool.

mcp__server__tool

Namespaced adapters generated from the cached catalog, such as mcp__notion__search_pages.

Safety model

  • MCP server config is external integration config, not a trust grant.
  • Local stdio servers run commands with your OS permissions. Review command, args, cwd, and env before enabling.
  • MCP server descriptions, tool descriptions, and outputs are external content and should be treated as untrusted.
  • Use Heddle tool approvals and traces to review what MCP tools are called and why.

Related docs