DocsWhy AscribeGitHub

Set up the MCP server

Give an agent with no shell Ascribe’s answers as tools, through ascribe mcp.

For AI agents: the documentation index is at llms.txt, and this page is available as Markdown.

ascribe mcp is a server for the Model Context Protocol, which most agents’ hosts speak. It offers the commands that answer questions as tools an agent calls, for an agent with no shell, or a host that asks you to approve each command it runs. An agent with a shell needs no server: the commands give the same answers.

In VS Code, the extension offers the server itself, so there’s nothing to set up: see Agents in the editor. In Claude Code, the plugin has it, and ascribe agents sync --target claude --with-hook writes it into .mcp.json.

Add the server to your agent’s host

Your agent’s host starts the server, in the repository’s root, and one server serves every project in it.

  1. Open the file your host reads its servers from, such as .mcp.json at the repository’s root for Claude Code, or .cursor/mcp.json for Cursor.

  2. Add Ascribe to it:

    {
  "mcpServers": {
    "ascribe": {
      "command": "npx",
      "args": ["ascribe", "mcp"]
    }
  }
}

  3. Start a new session, and check that the host lists the server’s tools.

What it offers

Its tools are the commands that answer questions; its resources are each directive’s syntax, and each project’s content model and rules; and its prompts are new-page, fix, and review, which many hosts show as slash commands. Every tool is read-only, so ascribe_check never runs Vale: ascribe check --vale in a shell, which your host asks you about, checks the prose. A tool’s result is its command’s JSON, whose schema is in the JSON report contract, and no tool gives an output schema, which would make the tool list five times as long. ascribe mcp lists each tool and the command it runs, and the resources.