MCP Client Setup

Tanda's AI assistant and tools are available over the Model Context Protocol. Connection requires a client with compatible protocol support, Streamable HTTP, and OAuth. Setup instructions below cover Claude Code, Claude Desktop, claude.ai, Cursor, ChatGPT, Codex, and Pi. Your assistant can then read your projects and statements of work, add task items, acceptance criteria and tests, draft whole SOWs for your approval, find coverage gaps, and work with requests for change (RFCs) and root cause analyses (RCAs).

Endpoint: https://agents.testandaccept.com/mcp Transport: Streamable HTTP Authentication: OAuth. You sign in with your Tanda account; there's no API key to copy.

claude mcp add --transport http tanda https://agents.testandaccept.com/mcp

claude mcp add --transport http tanda https://agents.testandaccept.com/mcp --header "Tanda-Organization: acme"

{
  "mcpServers": {
    "tanda": {
      "url": "https://agents.testandaccept.com/mcp",
      "headers": { "Tanda-Organization": "acme" }
    }
  }
}

codex mcp add tanda --url https://agents.testandaccept.com/mcp
codex mcp login tanda

pi mcp add tanda --url https://agents.testandaccept.com/mcp
pi mcp login tanda
pi mcp list

{
  "mcpServers": {
    "tanda": {
      "type": "http",
      "url": "https://agents.testandaccept.com/mcp",
      "headers": { "Tanda-Organization": "acme" }
    }
  }
}

Choosing a Default Organization

If you belong to several Tanda organizations, tools that list or create things need to know which one you mean. Rather than naming it in every request, choose it once:

• Desktop and web apps (Claude, ChatGPT): tell the assistant, for example "Work in Acme from now on." It calls set_default_organization, and Tanda remembers the choice for that connection until you change it ("Clear my default Tanda organization"). Each connection has its own default, so your Claude and ChatGPT connections can differ.
• IDEs and command-line tools (Claude Code, Cursor, Codex): send a Tanda-Organization header with the organization's slug, name or ID. Set it per repository in that repository's MCP configuration, as in the examples above, and each project defaults to its own organization.

When a request names an organization, that always wins. Then the header, if your client sends one; then the stored default; then your only organization, if you have just one. Tools that take a record ID (a SOW, task item or criterion) work in that record's organization regardless. Tanda checks your membership on every request: a default for an organization you've left is ignored, and a header naming one you don't belong to is refused.

Ask "Which Tanda organization am I working in?" at any time: list_organizations reports the default in effect and where it comes from.

What You Can Do

For connected repository tests, follow the IDE testing workflow or automated acceptance testing guide. A runner connection is required before code tests can execute.

Troubleshooting

Removing the Connection

claude mcp remove tanda

On claude.ai, remove the connector under Settings → Connectors. For JSON-configured clients, delete the tanda entry and restart.

Native client callback errors

Pi, Codex, and other native clients return from browser sign-in to a registered local callback such as http://127.0.0.1:45123/callback. Tanda permits the port to change between logins, while requiring the hostname, path, and query to match the registration. localhost, 127.0.0.1, and [::1] are separate callback hosts.

If sign-in returns invalid_redirect, restart the client's MCP login to generate a fresh authorization URL. If you changed the callback hostname or path, clear that client's Tanda OAuth registration and reconnect so it can register the new callback. Do not replace the callback with the Tanda website URL; the local MCP client needs to receive the authorization response. When reporting a persistent failure, include only the client_id and redirect_uri from the generated URL, not tokens or authorization codes.