Community MCP catalogue¶
Third-party MCP servers Gaby knows about. Picking one of these in the Connectors UI pre-fills the spawn command + the env variables it expects, so the only thing you provide is the secret.
Inclusion here means someone on the Gaby side has skimmed it and confirmed
it works with the host's stdio + tools/list handshake. It is not a
security audit. Read the linked source before you wire one up.
Developer tools¶
| MCP | What it gives the agent | Upstream |
|---|---|---|
| GitHub | Repo, issue, PR, code-search reads. | @modelcontextprotocol/server-github |
| GitLab | Projects, issues, MRs, pipeline status. | @modelcontextprotocol/server-gitlab |
| Linear | Issues, projects, cycles, team members. | linear-mcp-server |
| Atlassian (Jira + Confluence) | Jira issues + Confluence pages. Great when runbooks live there. | mcp-atlassian |
Communication¶
| MCP | What it gives the agent | Upstream |
|---|---|---|
| Slack | Channels, messages, user directory. Note: Slack as an escalation channel uses a separate code path; see escalation guide. | @modelcontextprotocol/server-slack |
Documentation¶
| MCP | What it gives the agent | Upstream |
|---|---|---|
| Notion | Read pages, databases, workspace search. | @notionhq/notion-mcp-server |
Infrastructure¶
| MCP | What it gives the agent | Upstream |
|---|---|---|
| Filesystem | Read files from a scoped local path. Useful for runbooks checked out next to Gaby. | @modelcontextprotocol/server-filesystem |
| Cloudflare | DNS records, Workers, KV, R2, zone analytics. | @cloudflare/mcp-server-cloudflare |
Observability¶
| MCP | What it gives the agent | Upstream |
|---|---|---|
| PagerDuty | Read incidents, services, on-call schedules. Doesn't trigger pages (that's escalation's job). | pagerduty-mcp-server |
| Datadog | Logs, metrics, monitors, dashboards. | @winor30/mcp-server-datadog |
How to enable one¶
- Settings → Connectors → Add.
- Pick the connector. The form pre-fills
Command+Args. - Fill in the required env vars (each row lists them).
- Save. Gaby spawns the subprocess and runs the handshake.
npx / uvx must be on the backend's PATH. The Docker image ships both;
custom installs need to install them.
Not on the list?¶
Use Bring your own MCP. If it's something a lot of teams would want, open an issue and we'll add it.