Connectors
Connectors provide a unified interface to external integrations, whether backed by MCP servers or built-in skills. Each connector tracks its connection status and configuration, giving you a single place to manage all integrations.
Built-in connectors
Section titled “Built-in connectors”| Connector | Type | Backend |
|---|---|---|
| Google Drive | MCP | mcp/gdrive Docker image |
| GitHub | MCP | mcp/github Docker image |
| Gmail | MCP | mcp/gmail Docker image |
| Google Calendar | MCP | mcp/google-calendar Docker |
| PostgreSQL | MCP | mcp/postgres Docker image |
| MySQL | MCP | mcp/mysql Docker image |
| Redis | MCP | mcp/redis Docker image |
| MongoDB | MCP | mcp/mongodb Docker image |
| n8n | MCP | mcp/n8n Docker image |
| Slack | MCP | mcp/slack Docker image |
| Jira | MCP | mcp/jira Docker image |
| Linear | MCP | mcp/linear Docker image |
| Sentry | MCP | mcp/sentry Docker image |
| Datadog | MCP | mcp/datadog Docker image |
| Notion | MCP | mcp/notion Docker image |
Connection status
Section titled “Connection status”Each connector has one of four states:
| Status | Meaning |
|---|---|
| connected | Running and responding to requests |
| disconnected | Not configured or not started |
| configuring | Setup in progress (e.g., waiting for API key) |
| error | Started but failed (bad credentials, network issue) |
Status is persisted in the codebuddy.connectors.states setting so your connector states survive editor restarts.
How connectors work
Section titled “How connectors work”
graph LR
A["ConnectorService"] --> B{"Connector type?"}
B -->|MCP| C["MCPService<br/>stdio or SSE transport"]
B -->|Skill| D["SkillService<br/>Built-in TypeScript implementation"]
C --> E["MCP Server Process"]
D --> F["Direct API calls"]
The ConnectorService syncs with the MCPService on initialization:
- Reads built-in connector definitions
- Checks which MCP servers are currently running
- Updates connector statuses to match MCP server states
- Monitors MCP server events (connect, disconnect, error)
Configuration
Section titled “Configuration”Connecting a connector
Section titled “Connecting a connector”When you connect a connector:
- The service generates the MCP server configuration (Docker image, args, env vars)
- Injects configuration into
codebuddy.mcp.servers - Starts the MCP server via
MCPService - Updates the connector status to
connected
Disconnecting
Section titled “Disconnecting”Disconnecting a connector:
- Stops the MCP server process
- Removes the server from
codebuddy.mcp.servers - Sets connector status to
disconnected
Settings
Section titled “Settings”| Setting | Type | Default | Description |
|---|---|---|---|
codebuddy.connectors.states | object | {} | Persisted connection states per connector |