Connectors

Connectors are a unified UI over MCP servers and built-in skills. Each connector tracks connection status and configuration in one place.

Built-in connectors

All MCP-backed via Docker images:

Connector	Docker image
AWS	`mcp/aws`
GitHub	`mcp/github`
GitLab	`mcp/gitlab`
Gmail	`mcp/gmail`
Google Calendar	`mcp/google-calendar`
Google Drive	`mcp/gdrive`
Jira	`mcp/jira`
Kubernetes	`mcp/kubernetes`
Linear	`mcp/linear`
MongoDB	`mcp/mongodb`
MySQL	`mcp/mysql`
n8n	`mcp/n8n`
Notion	`mcp/notion`
PostgreSQL	`mcp/postgres`
Redis	`mcp/redis`
Sentry	`mcp/sentry`
Slack	`mcp/slack`

Status

Each connector has one of four states:

Status	Meaning
`connected`	Running + responding
`disconnected`	Not configured or not started
`configuring`	Setup in progress (waiting for API key, etc.)
`error`	Started but failed (bad creds, network issue)

Persisted in codebuddy.connectors.states so states survive editor restarts.

How they work

graph LR A[ConnectorService] --> B{Type?} B -->|MCP| C[MCPService<br/>stdio or SSE transport] B -->|Skill| D[SkillService<br/>Built-in TypeScript impl] C --> E[MCP server process] D --> F[Direct API calls]

ConnectorService syncs with MCPService on init:

Read built-in connector definitions.
Check which MCP servers are running.
Update connector statuses.
Monitor MCP server events (connect / disconnect / error).

Connect + disconnect

Connect:

Generate MCP server config (Docker image, args, env vars).
Inject into codebuddy.mcp.servers.
Start via MCPService.
Status → connected.

Disconnect:

Stop MCP server process.
Remove from codebuddy.mcp.servers.
Status → disconnected.

Settings

Setting	Default	Purpose
`codebuddy.connectors.states`	`{}`	Persisted connection states per connector

MCP — the transport underneath most connectors
Skills — the skill-backed alternative for some integrations
Docker integration — Docker gateway that many connectors use