Hosted MCP server/Memory

todox MCP server

Hosted at www.todox.dev·Streamable HTTP

todox is a shared session log for coding agents and people. It records decisions, dead ends, handoffs and open tasks so the next session can resume, flags stale notes instead of inventing outcomes, and builds reports from the log. It can be hosted or self-hosted under the MIT license. The documented install path is pnpm install:mcp <client> --token todox_..., which writes the config, verifies the connection and supports --dry-run. The token is required and can also come from $TODOX_TOKEN or an interactive prompt.

www.todox.dev Streamable HTTP API key (Bearer todox_...) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Developers who move work between Claude Code, Codex, Cursor, VS Code and other agents and need a durable handoff log.

  • Resume a session from logged decisions and open tasks.
  • Hand off unfinished work to another agent or teammate.
  • Flag stale notes while reviewing project history.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Install todox MCP

Run the provider installer from a checkout of the todox repository. It writes the client config, verifies the connection and accepts a token from --token, $TODOX_TOKEN or an interactive prompt. Add --dry-run to print the plan without writing.

  1. Create a todox token

    Generate a todox_ token for the workspace, or reuse an existing one. The installer fails without a token.

  2. Run the provider installer

    Choose one of the five documented clients: claude-code, codex, cursor, vscode or opencode.

    pnpm install:mcp claude-code --token todox_...
  3. Or add the hosted endpoint by hand

    Client-native setup is a secondary path. It still needs the Authorization header.

    claude mcp add --transport http todox https://www.todox.dev/api/mcp --header "Authorization: Bearer todox_..."

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://www.todox.dev/api/mcp
Host
www.todox.dev · /api/mcp
Transport
Streamable HTTP
Authentication
API key (Bearer todox_...)
Server name
todox
Listing type
Community or directory listing

The installer uses the server name todox. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that todox appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Resume a session from logged decisions and open tasks. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

todox documentationhttps://github.com/beydemirfurkan/todox/blob/HEAD/docs/mcp.mdGitHub repositoryhttps://github.com/beydemirfurkan/todox