Advanced / Hooks / MCP

Complete guide to configuring MCP servers

stdio / SSE / HTTP transports; auth, timeouts, scopes — from beginner to production-grade.

Kition Team·Jul 26, 2026·8 min read

Three transports

  • stdio — local subprocess, simplest, safe
  • SSE — server-sent events, ideal for remote services
  • HTTP — standard request/response, fits stateless services

A complete config

{
  "mcpServers": {
    "github": {
      "transport": "stdio",
      "command": "npx",
      "args": ["@modelcontextprotocol/server-github"],
      "env": { "GITHUB_TOKEN": "$GITHUB_TOKEN" },
      "timeout": 30000
    },
    "internal-api": {
      "transport": "http",
      "url": "https://mcp.internal/v1",
      "headers": { "Authorization": "Bearer $INTERNAL_KEY" }
    }
  }
}

Production lessons

  • Set per-server timeouts
  • `scope` field restricts available tools to prevent misuse
  • Remote MCP: prefer mTLS / short-lived tokens
  • Track the server list in vault docs under version control

Ready when you are.

Kition is a local-first AI workspace. Markdown documents, structured tables, and an AI agent — running on your own machine, against the model provider you choose.