MCP Server

What decision-anchor/mcp-server MCP server does

The decision-anchor/mcp-server MCP server provides the MCP interface for Decision Anchor. Its purpose is to record accountability boundaries on both sides of an interaction without evaluating or interpreting the underlying content. The adapter forwards tool requests to Decision Anchor’s public HTTP API at api.decision-anchor.com rather than maintaining its own records.

The hosted endpoint is available at https://mcp.decision-anchor.com/mcp and uses streamable HTTP. The project is also listed in the MCP Registry as com.decision-anchor/da. This makes the remote service suitable for clients that can connect to an MCP server over HTTP without installing the repository locally.

How it works

The decision-anchor/mcp-server MCP server exposes 30 tools. The available groups cover decision declarations identified as DD/EE, bilateral agreements, observation through ARA, sessions through SDAC/ISE, and account management. The server’s tools/list response is the authoritative source for the currently exposed tool names and schemas.

Authenticated tools accept an auth_token argument. Instead of passing the token with every call, a client can send it in the connection’s authorization header. An explicit tool argument takes precedence over the connection-level token. Registering an agent while a connection already carries a token still creates a second identity, according to the project documentation.

The adapter itself does not hold a database, payment keys, or application state. Registration does not require prior authentication and provides a free trial balance. Once that balance is used, calls are paid per use in USDC through x402 on Base. Prices are retrieved from the live API rather than defined by this repository.

Setup and configuration

For hosted use, configure an MCP client with the streamable HTTP URL and, when needed, an authorization header such as Bearer ${DA_AUTH_TOKEN}. The README specifically documents header configuration for Claude Code, Cursor, VS Code, and Gemini CLI. Claude Desktop can connect through mcp-remote with the documented header syntax.

A local checkout can be started with npm ci followed by node index.js. HTTP mode listens on the PORT environment variable and defaults to port 3003. Set DA_API_URL to direct the adapter to another API endpoint, such as a test service. Running without --http starts a local stdio server; in that mode, DA_AUTH_TOKEN can be placed in .env so calls may omit the token argument.

DA_AUTH_TOKEN is rejected in HTTP mode. This prevents a shared HTTP process from assigning one configured identity to every anonymous caller.

Tools and capabilities

The decision-anchor/mcp-server MCP server supports these documented capability areas:

• Decision declarations, including DD/EE
• Bilateral agreements
• Observation through ARA
• Sessions through SDAC/ISE
• Account management

For exact parameters and current operations, consult the live tools/list response, the published openapi.json, or the agent-oriented llms.txt documentation.

Limitations and notes

It is a thin API layer, so availability and current pricing depend on the hosted Decision Anchor API. Paid usage begins after the free trial balance and requires USDC settlement through x402 on Base.

The repository can run locally, but local execution still forwards requests to the configured API. No local database or independent persistence layer is described. The Apache-2.0 license applies to the project.