Documentation Navigation
Extend

MCP servers

Paste any MCP config and tools appear on connect.

The runtime is dynamic: a server's tools load the moment it connects, with cross-platform binary resolution handled for you.

#Local servers

Local server config
{
  "name": "sqlite",
  "type": "local",
  "command": ["npx", "server-sqlite"],
  "env": { "DB_PATH": "/data/app.db" }
}
  • Type: local spawns the command on your machine.
  • Command: resolved cross-platform, e.g. npx server-sqlite.
  • Env: pass secrets like DB_PATH without baking them into the command.

#Remote servers

Remote server config
{
  "name": "api",
  "type": "remote",
  "url": "https://api.example.com/mcp",
  "headers": { "Authorization": "Bearer <token>" }
}
  • Type: remote connects over HTTP to the given URL.
  • Auth: attach a token with the Bearer scheme in headers.

#Auth

OAuth uses PKCE with an automatic browser flow, and tokens are stored in ~/.local/share/codey/mcp-auth.json.

The old n8n integration is retired.

#See also

Skills · Custom tools · Configuration