Claude Integration

Connect Claude to Tanda, and Claude can read your projects and statements of work, add task items, acceptance criteria and tests, draft whole SOWs for your approval, point out what isn't tested yet, and run your change control: requests for change (RFCs) and root cause analyses (RCAs).

Quick Setup

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

Connecting Claude, step by step

This walks through adding Tanda as a custom connector on claude.ai or Claude Desktop. Connectors you add on claude.ai also appear in Claude Desktop, so you only do this once.

Working with multiple organizations

One connection works in every Tanda organization you belong to. Name the organization in your request, and Claude passes it along:

• "List my Tanda organizations."
• "In Acme, list my projects."
• "Show the SOWs in Beta Labs that are still in draft."

You can use an organization's name or its short slug. If you belong to only one organization, you never need to name it. When you ask about a specific SOW, task item or criterion, Claude works in the organization that record belongs to. Every answer says which organization it came from.

To stop naming it, choose it once: "Work in Acme from now on." Claude calls set_default_organization, and Tanda remembers the choice for this connection until you change it. "Which Tanda organization am I working in?" shows the default in effect, and "Clear my default Tanda organization" removes it. Naming another organization in a request still works for that request.

You never reach more than your account allows. Tanda checks your membership on every request, so leaving an organization takes effect immediately.

Claude Code

Claude Code doesn't show this dialog. Run:

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

Then run /mcp, select tanda, choose Authenticate, and complete the same sign-in and access steps in your browser.

The command above adds Tanda to the current project only. To use it in every project, add --scope user. To share it with everyone on a repository, commit a .mcp.json file instead (see MCP Client Setup).

If you belong to several organizations, tell Claude Code which one this project works in, so you never have to name it:

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

Or in .mcp.json, add "headers": { "Tanda-Organization": "acme" } to the server entry. Use the organization's slug, name or ID. Each repository can point at its own organization, and your sign-in is shared across them.

What Claude Can Do

Explore

• Projects: list them and view one, including how many SOWs it has.
• Organizations: list the organizations you can work in.
• Statements of work: list them by project or across one of your organizations, and open one with its task items, acceptance criteria and tests.
• Task items, criteria and tests: list and inspect them at any level.

Build

• Create a draft SOW in a project.
• Add or update task items. Requirements go at the top level, and work items sit under them.
• Add or update acceptance criteria. Claude writes them as Given/When/Then or as measurable assertions.
• Add tests for a criterion.

Manage change: RFCs and root cause analyses

• Requests for change (RFCs): list them by project, status or keyword, and open one with its sections and linked SOW versions. Claude can open a new RFC with structured sections (problem, proposed solution, alternatives, risks, implementation plan and so on), revise it while it's open, and close it, or mark it ADR created, once a decision is made. See RFCs.
• Root cause analyses (RCAs): list and open them, start one for an incident, defect or failed acceptance test, then fill in the timeline, root cause, reasoning, solutions and how you'll measure success as the investigation goes. Until a root cause is agreed, Claude walks you through the five whys, one question at a time, and saves the chain on the RCA. Mark it complete when it's agreed. See Root Cause Analyses.
• SOW versions: list a SOW's versions, and link an RFC or RCA to the version it concerns. An RFC addresses, was created from, or supersedes a version. An RCA's issue was introduced in, identified in, or resolved by a version.

An RFC or RCA belongs to a project, and you need access to that project to see it, plus write access to change it. A closed RFC is locked: Claude can only reopen it, by changing its status back to open.

Analyze

• Coverage: which task items and criteria have tests, and the overall percentage.
• Completeness: task items missing descriptions, criteria or tests, with suggested fixes.
• Coverage gaps: proposed acceptance criteria and tests to fill them. Nothing is saved until you accept.
• Ask Tanda: a question about your data that spans many records. Follow-up questions in the same conversation keep the context.

Generate a SOW (with your approval)

Describe the work and Claude starts a SOW generation run. Tanda drafts the title and summary, task items, acceptance criteria and proposed tests, then pauses for your approval. Nothing is saved until you approve, and rejecting discards the draft.

"Draft a SOW in project Website Rebuild for moving the marketing site to a headless CMS,
 with analytics and a launch plan. Show me the draft before creating anything."

Claude can configure, start, and inspect code test runs when an administrator has connected a repository runner. See the IDE testing workflow for linking code to criteria and sharing results with your team.

Example Requests

"What SOWs are in project Mobile App?"
"Add a requirement 'Users can reset their password' to SOW Phase 2, with two acceptance criteria."
"For each criterion in task Checkout without tests, propose one test, then add the ones I approve."
"How complete are the requirements in SOW Phase 2?"
"Find coverage gaps in SOW Phase 2 and suggest criteria for them."
"Open an RFC in project Mobile App to add single sign-on, with problem, solution and risks sections."
"List the open RFCs in Website Rebuild and summarize what each one changes."
"Start a root cause analysis for last night's checkout outage, severity high, and link it to SOW Phase 2 v1.3 as the version that introduced it."
"Walk me through the five whys for the checkout outage RCA."
"Close RFC-2026-004: we accepted it. Add the decision and rationale first."

Security & Privacy

• You sign in with your own Tanda account. Claude never sees your password, and there's no shared API key.
• Access follows your permissions. Claude can reach only the organizations you belong to, and within them only the projects and SOWs your account can. Membership is checked on every request.
• Read and write are separate. Without Write access, Claude can look but not change anything.
• Missing and inaccessible records look the same. Both return the same "does not exist or you do not have access" message, so IDs can't be probed.
• You can disconnect anytime: claude mcp remove tanda, or remove the connector in claude.ai.

Troubleshooting

Claude asks you to sign in, or tools return 401

Your session expired or you haven't connected yet. In Claude Code, run /mcp → tanda → Authenticate. In claude.ai, reconnect the connector.

"you belong to several organizations; pass organization to choose one"

Name the organization in your request, for example "in Acme, list my projects", or choose one once with "Work in Acme from now on" (see Working with multiple organizations). In Claude Code, you can instead set a Tanda-Organization header (see Claude Code).

"this connection is limited to …"

The connection was made before multi-organization support and is tied to one organization. Reconnect once to reach all of them (see Working with multiple organizations).

403 insufficient_scope when creating or updating

You didn't grant Write access. Reconnect and approve it.

"does not exist or you do not have access"

The ID is wrong, the record is in an organization you don't belong to, or your account can't access that project or SOW. Ask a project owner to share it with you.

Sign-in fails right after you click Connect

Check the connector's OAuth client setting. It must be Register automatically. Remove the connector and add it again with that option.

Claude Code still connects to an old Tanda URL

An older entry can override the project's .mcp.json. Run claude mcp list to see which URL Claude Code uses. Then remove the stale entry from the scope it lives in, for example claude mcp remove tanda -s local, and restart Claude Code.

The connector points at mcp.testandaccept.com

That endpoint has been retired. Remove the connector and add https://agents.testandaccept.com/mcp.