Connectors & MCP

Base URL: https://api.guilde.work/guilde/api/v1

Connectors are integrations that provide capabilities to operators. There are three types:

Platform connectors — Built-in integrations (CMS, CRM, analytics, etc.)
MCP connectors — User-provided MCP servers that add custom tools to operators
Hosted MCP — Pre-built MCP servers from the catalog (Notion, GitHub, Slack, Linear)

Guild Connectors

List connectors

curl https://api.guilde.work/guilde/api/v1/guilds/{guildId}/connectors \
  -H "Authorization: Bearer gld_your_api_key"

Add connector

curl -X POST https://api.guilde.work/guilde/api/v1/guilds/{guildId}/connectors \
  -H "Authorization: Bearer gld_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "mcp",
    "settings": {
      "type": "external",
      "slug": "my-api",
      "url": "https://mcp.example.com/sse"
    }
  }'

When adding an MCP connector, the server is probed automatically to discover available tools. Tool definitions are cached in the connector metadata.

Remove connector

curl -X DELETE https://api.guilde.work/guilde/api/v1/guilds/{guildId}/connectors/{connectorId} \
  -H "Authorization: Bearer gld_your_api_key"

MCP Connectors

Types

Type	Description
`external`	Your own MCP server URL
`hosted`	Pre-built server from catalog (we host it)
`sandbox`	Custom package running in E2B sandbox

External MCP

{
  "provider": "mcp",
  "settings": {
    "type": "external",
    "slug": "my-tools",
    "url": "https://mcp.mycompany.com/sse",
    "headers": { "Authorization": "Bearer secret" }
  }
}

Hosted MCP (from catalog)

{
  "provider": "mcp",
  "settings": {
    "type": "hosted",
    "slug": "notion",
    "serviceId": "notion",
    "credentials": { "apiKey": "ntn_..." }
  }
}

Sandbox MCP

{
  "provider": "mcp",
  "settings": {
    "type": "sandbox",
    "slug": "custom-server",
    "runtime": "node",
    "package": "@my-org/mcp-server",
    "env": { "API_KEY": "..." }
  }
}

Sandbox servers start on first tool call (lazy provisioning) and auto-shutdown after 30 minutes of inactivity.

Browse catalog

curl https://api.guilde.work/guilde/api/v1/guilds/{guildId}/connectors/mcp/catalog \
  -H "Authorization: Bearer gld_your_api_key"

Returns available hosted MCP servers (Notion, GitHub, Slack, Linear) with their required credentials.

Refresh tools

Re-probe an MCP server to update cached tool definitions:

curl -X POST https://api.guilde.work/guilde/api/v1/guilds/{guildId}/connectors/{connectorId}/refresh \
  -H "Authorization: Bearer gld_your_api_key"

Assigning MCP to operators

MCP connectors become capabilities with the mcp: prefix. To give an operator access to an MCP server with slug notion:

curl -X PUT https://api.guilde.work/guilde/api/v1/guilds/{guildId}/operators/{operatorId} \
  -H "Authorization: Bearer gld_your_api_key" \
  -d '{ "capabilities": ["company", "document", "mcp:notion"] }'

User Connectors

List my connectors

curl https://api.guilde.work/guilde/api/v1/connectors/me \
  -H "Authorization: Bearer gld_your_api_key"

List available providers

curl https://api.guilde.work/guilde/api/v1/connectors/providers \
  -H "Authorization: Bearer gld_your_api_key"

Health Check

curl https://api.guilde.work/guilde/api/v1/guilds/{guildId}/connectors/health \
  -H "Authorization: Bearer gld_your_api_key"

Returns health status, latency, and errors for each guild connector.

Connectors & MCP

On this page