Skip to content

Docs MCP Server

Kyku provides a Model Context Protocol (MCP) server that exposes documentation as resources and tools for AI coding agents. This allows agents to query documentation at runtime without needing to crawl the docs site.

The Model Context Protocol (MCP) is an open standard that lets AI applications connect to external tools and data sources. An MCP server exposes:

  • Resources: Readable data (files, docs, schemas)
  • Tools: Callable functions for actions
  • Prompts: Reusable prompt templates

The Kyku docs MCP server provides:

Resource URI Description
docs://providers/index Provider parity matrix
docs://providers/aws AWS provider details
docs://providers/gcp GCP provider details
docs://providers/hetzner Hetzner provider details
docs://providers/digitalocean DigitalOcean provider details
docs://providers/kubernetes Kubernetes provider details
docs://internals/engine Engine lifecycle
docs://internals/dependency-graph Graph builder internals
docs://internals/diff-engine Diff engine internals
docs://internals/planner Planner internals
docs://internals/crypto Encryption architecture
docs://internals/auth Auth modules
docs://internals/decisions Architecture decision log
docs://guides/deploy-web-app Deploy web app guide
docs://guides/ci-cd CI/CD guide
docs://guides/environments Environment management
docs://guides/state-encryption State encryption deep dive
docs://guides/import-resources Resource import guide
docs://agents/index AI agents overview
docs://agents/llms-txt llms.txt standard
docs://agents/contributor-context AGENTS.md conventions
docs://roadmap Feature roadmap
Tool Description
search-docs Search documentation by query
get-provider-details Get details for a specific provider
get-resource-types List all supported resource types
get-credential-requirements Get credential requirements for a provider
Prompt Description
create-kyku-config Generate an Kyku config for common patterns
troubleshoot-provider Diagnose provider configuration issues
migrate-existing-infra Plan migration from other IaC tools

Add to your claude_desktop_config.json:

{
"mcpServers": {
"kyku-docs": {
"command": "bun",
"args": ["run", "packages/docs-mcp-server/src/index.ts"]
}
}
}

The server runs on stdio transport by default:

Terminal window
bun run packages/docs-mcp-server/src/index.ts

Or as an HTTP server:

Terminal window
KYKU_MCP_HTTP=true bun run packages/docs-mcp-server/src/index.ts
# Listens on http://localhost:3100

When an AI agent needs Kyku documentation during a task:

  1. The agent discovers the MCP server via its configuration
  2. For specific docs, it reads the relevant resource URI
  3. For open-ended questions, it uses search-docs
  4. For code generation, it uses create-kyku-config prompt

This avoids the need to:

  • Crawl the docs site
  • Hardcode documentation URLs
  • Parse HTML/markdown manually

The MCP server is built with the official @modelcontextprotocol/sdk and reads markdown files from the docs site build output. It’s maintained in packages/docs-mcp-server/.