discord-manager: Skill for Claude Code

MCP Server

Everything here documents the repository as it is on main. If main disagrees with this file, main wins: follow it and flag the drift.

Discord Manager has no web UI. The MCP server is how the owner uses the product: an MCP client spawns pnpm run mcp over stdio and calls tools that are thin projections of the business layer. The rule that keeps this honest: the MCP server never serves more, and never less, than the business layer serves the owner — enforced by the parity test.

Architecture map

app/mcp/
  tool.ts                   McpTool shape (name, description, inputSchema, wraps, execute)
  server.server.ts          stdio server: listTools / callTool dispatch, JSON-schema projection
  registry.server.ts        accumulate-only array of every domain's tools
  tools/<domain>.server.ts  one array per domain (channelsTools, bookmarksTools, …)
  run.ts                    entrypoint — `pnpm run mcp`
  parity.test.ts            every business capability is wrapped xor exempt
  parity-exemptions.ts      business functions that are not owner capabilities, with a reason each

The server is stdio-only and single-owner. There is no network listener, no bearer token, no consent screen, and no scope model — the process is spawned by the owner's own client on the owner's own machine, and the configured owner is the only identity.

THE ONE RULE

A tool's execute is a single business-function call, passing the real owner context. No authorization lives in app/mcp/ — every gate is the business layer's own gate, reused:

• Capability is the business function's applySchema(input, contextSchema). The extended context schema carries z.literal(true) flags; a deployment that lacks a capability fails validation there, with the same error a job or a test would get.
• Data scoping and the final say belong to the same schema. If the business layer would deny it, it denies it here too, with the identical message.

Every registered tool is listed, always. There is no visibility filter in the MCP layer: hiding a tool would be an authorization decision, and authorization decisions live in the business layer. Denial surfaces from the call, not from the listing.