MCP Servers

Extend agents with external tools via Model Context Protocol. Stdio JSON-RPC, auto-discovered, namespaced.

How it works

Plug in any MCP server

Define a server in a Markdown file, reference it from your agent, and its tools appear automatically.

examples/mcp/jira.md
--- name: jira type: mcp_server transport: stdio command: - mcp-server-atlassian - --jira env: JIRA_URL: ${env:JIRA_URL} JIRA_TOKEN: ${secret:jira-token} tool_prefix: jira ---

Three steps to connect

  • Install the MCP server binary (pip, npm, or go install)
  • Create a .md definition file with connection details
  • Add mcp: [jira] to your agent's frontmatter

Tools are namespaced (jira__get_issue) to avoid collisions. The agent discovers available tools automatically via JSON-RPC handshake.

Included

Ships with the repo

GitHub
PR/issue/repo operations. Create PRs, search issues, manage repos. Used by the coder.md agent.
Included
Jira
Search, read, create, update, and transition issues. JQL queries. Used by ticket-worker.md.
Included
Confluence
Search, read, create, and update pages. CQL queries. Used by ticket-worker.md.
Included
Compatible

Community MCP servers that work with AgentCTL

Stdio, HTTP, and SSE transports are all supported. Any MCP-compliant server works.

kubectl
Structured Kubernetes operations — pod status as JSON, safe delete guards, namespace scoping.
Community
Terraform
Plan parsing, state inspection, resource graph queries. Structured plan output instead of raw text.
Community
Slack
Send messages, read channels, search history. Useful for notification agents and ChatOps.
Community
PostgreSQL
Query databases, inspect schemas, run migrations. Read-only mode for safety.
Community
Docker
Container management, image inspection, log streaming. Pairs with the DevOps agents.
Community
AWS
CloudFormation, S3, Lambda, ECS operations. Structured responses for infrastructure agents.
Community
Brave Search
Web search for agents that need to look up documentation, APIs, or current information.
Community
Email (SMTP)
Send emails, read inbox. Useful for notification workflows and report delivery.
Planned
HTTP/SSE Transport
HTTP and SSE transports are fully supported. Use transport: http or transport: sse in your MCP server definition.
Supported