mcp

Documentation

Overview

Package mcp exposes the builder over the Model Context Protocol, so an agent running anywhere — Claude Code, Codex, any MCP client — can read the issue board and talk to this fleet and its memory.

Two servers rather than one, because they have very different blast radii:

/mcp/feedback — the issue plane. File issues, read them, comment, move them.
/mcp/agents   — the fleet: personas, skills, and each agent's brain.

A token wired into a shared editor should be able to file bugs without also being able to read what every agent has learned, so the scope is part of the credential rather than a convention.

Index

• type Service
  • func New(db *sql.DB, log *slog.Logger) *Service
  • func (s *Service) Routes(r chi.Router)

Types

type Service

type Service struct {
	// contains filtered or unexported fields
}

func New

func New(db *sql.DB, log *slog.Logger) *Service

func (*Service) Routes

func (s *Service) Routes(r chi.Router)

Routes mounts both MCP servers and the token management the dashboard uses.

The two servers are separate URLs rather than one server with per-tool permission checks. A client asks a server what it can do; if the answer depended on the token, the same URL would advertise different capabilities to different callers, and an operator reading the connect instructions could not tell what they were about to grant.