Todia Remote MCP

Share the task.
Let your AI agent execute.

Todia is where your team manages a task’s purpose, deadline, and progress. AI agents such as Claude Code, Codex, and GitHub Copilot can use that context to implement, investigate, and fix work outside Todia.

People stay in control

Agents execute work.
People approve Todia changes.

MCP can search tasks and events, then propose creation, completion, or reopening. Every proposal is reviewed in Todia Web before it is applied. An agent never finalizes a Todia record directly.

  1. 01

    Manage in Todia

    Keep the task’s purpose, deadline, owner, and progress together.

  2. 02

    Agent executes

    The agent searches context through MCP, then implements, investigates, or fixes work in its permitted environment.

  3. 03

    Approve in Web

    Review the agent’s proposals; only approved changes are applied.

Shared prerequisites

First, prepare your
connection in Todia Web.

  1. 1

    Sign in to Todia Web

    Sign in with Google or a verified-email account.

  2. 2

    Open Settings → AI Agent access

    Copy the current Remote MCP endpoint and create a 30-day personal access token.

  3. 3

    Keep the token secure

    The token is shown once at issuance. Keep it only on a trusted local machine—never in Git, chat, or logs.

Client setup

Add the connection to your agent.

Claude Code

Add it as a local configuration

Run this in a terminal. Set the PAT as an environment variable; do not put it in shell history.

export TODIA_MCP_TOKEN='YOUR_PAT'
claude mcp add-json todia '{"type":"http","url":"TODIA_MCP_URL","headers":{"Authorization":"Bearer ${TODIA_MCP_TOKEN}"}}'

Verify with claude mcp get todia or /mcp in Claude Code.

Codex

Add it to config.toml

Add this to ~/.codex/config.toml, or a trusted project’s .codex/config.toml.

[mcp_servers.todia]
url = "TODIA_MCP_URL"
bearer_token_env_var = "TODIA_MCP_TOKEN"
default_tools_approval_mode = "prompt"

Set the environment variable, restart Codex, and check codex mcp list or /mcp in the TUI.

GitHub Copilot

Add it to VS Code user MCP configuration

Run MCP: Open User Configuration from the Command Palette and use a password input for the PAT. Do not share a personal token in workspace configuration.

{
  "inputs": [{
    "type": "promptString", "id": "todia-token",
    "description": "Todia personal access token", "password": true
  }],
  "servers": { "todia": {
    "type": "http", "url": "TODIA_MCP_URL",
    "headers": { "Authorization": "Bearer ${input:todia-token}" }
  }}
}

Trust and start it from the MCP Servers view or MCP: List Servers, then use it from Agent mode chat.

Client interfaces and configuration formats can change. If setup fails, consult the product’s official MCP documentation.

Daily workflow

From context to completion.

  1. Choose a task

    Record its purpose, deadline, and definition of done in Todia.

  2. Ask the agent

    Example: “Find ‘Implement auth flow’ in Todia, implement and test it in this repository, then propose completing the task.”

  3. Review the work

    Review the code changes, test results, and agent report. Todia proposals synchronize into AI Assistant.

  4. Approve in Todia Web

    Approving a proposal updates task state. The agent can check the final result with get_action_status.

Capabilities and limits

Move work forward,
with clear boundaries.

MCP can

  • Search personal and shared tasks and events
  • Propose task and event creation
  • Propose task completion or reopening
  • Check a proposal’s state

MCP cannot

  • Approve or directly apply a proposal
  • Delete or bulk edit records
  • Edit an existing event
  • Reveal a token after issuance