Codexrunledger MCP

What the codexrunledger-mcp MCP server does

The codexrunledger-mcp MCP server gives MCP-compatible AI clients access to a hosted Codex run ledger service. Its workflow centers on recording run receipts, describing the scope of work, identifying evidence that has not been supplied, and producing a handoff suitable for a client or reviewer.

The service is intended for development workflows where a reviewer needs more than a short completion message. It can organize changed-file evidence and proof checks around a Codex run, then expose the resulting information through MCP tools.

How it works

The codexrunledger-mcp MCP server uses a remote Streamable HTTP endpoint rather than a locally installed implementation. MCP clients send JSON-RPC requests to https://codexrunledger.clauxel.com/mcp. Production requests must include a bearer token in the HTTP authorization header.

The repository functions as public documentation and a directory-submission reference. It does not include the private production source code. A browser request without authentication receives a JSON error response rather than internal service details.

Setup and configuration

To use the codexrunledger-mcp MCP server, first open the product website and select a plan. Create or request an API token, then configure an MCP client that supports Streamable HTTP remote servers with the service endpoint.

Include the token on requests using this header format:

Authorization: Bearer <token>

The README does not specify a local package, startup command, or named environment variable. Configuration therefore consists of the hosted endpoint and the bearer credential in the MCP client. Pricing and access are managed through the product website.

Tools and capabilities

The codexrunledger-mcp MCP server exposes four tools:

• create_run_receipt creates a receipt for a Codex run.
• summarize_scope produces a summary of the work scope.
• list_missing_evidence checks which supporting proof or evidence is still missing.
• export_client_handoff exports a handoff receipt intended for client-facing delivery.

Together, these tools cover receipt creation, scope reporting, evidence review, and handoff preparation. The supplied material does not define their input schemas, output fields, retention behavior, or whether they read from external repositories.

Limitations and notes

The codexrunledger-mcp MCP server is a paid hosted service, so production use depends on obtaining a token and maintaining access to the selected plan. It is not presented as a self-hosted server, and the repository does not provide the production implementation.

The documentation identifies Streamable HTTP support as a client requirement but does not name specific MCP clients or provide client-by-client configuration examples. It also does not claim that the service performs code changes, runs tests, accesses a source-control provider, or stores evidence in a particular repository. OpenHuman Online is mentioned as a separate option for human-readable source memory, meeting notes, or approval context; it is not described as a dependency of this server.