kill9

Customize kill9

MCPs

Add, connect, validate, and manage MCP servers.

On this page

Open Settings → MCPs to review configured MCP servers and their tool scopes.

MCP (Model Context Protocol) servers add external tools that agents can call. An MCP server is a bridge between kill9 and an external service — a database, an API, an internal tool, or any system that exposes an interface.

What MCPs do

Without MCPs, agents can only use the tools built into kill9 — file operations, bash commands, web search. With MCPs, agents can query your database, call your internal API, or interact with any service you connect.

Examples:

  • Query a PostgreSQL database to check schema or data
  • Call a Stripe API to verify customer status
  • Interact with a Kubernetes cluster to check pod status
  • Access a custom internal service your team built

Finding MCPs

Open Settings → MCPs and go to the Browse tab. Filter for MCP servers. kill9 includes official integrations for common services, and you can add custom ones.

Connecting an MCP

Click Connect on an MCP server. Depending on the server, you may need to provide:

  • API key or authentication token
  • Server URL
  • Environment variables
  • Connection parameters

kill9 validates the connection before saving. Once connected, the tools provided by the MCP server appear in the agent's available tool list.

Managing MCPs

Connected MCPs appear in the Installed tab and in Tools (Mod+7) under the MCPs tab. Toggle them on or off. When off, agents cannot call that server's tools.