An agent can do all of this for you, without leaving your editor or terminal:
- Create an account and an organization.
- Invite people.
- Create a client and a project.
- Write a statement of work (SOW) with task items, acceptance criteria and tests.
- Produce the acceptance test plan (ATP).
From sign-up to ATP walks through every step. Give your agent that page, or use the prompt below.
Choose a route
There are two routes. They work on the same data, so you can mix them.
| Route | Sign-in | Use it when |
|---|---|---|
| REST API | An API token, created over HTTP | The agent can run shell commands, or nobody is there to open a browser |
| MCP | Your Tanda account in a browser, once | Your client supports MCP and you are at the keyboard |
| Where you work | Route | Set up |
|---|---|---|
| Claude Code | MCP or REST API | MCP setup |
| Codex | MCP or REST API | Codex |
| Cursor and other MCP IDEs | MCP or REST API | MCP setup |
| claude.ai and Claude Desktop | MCP | Claude |
| ChatGPT | MCP | ChatGPT |
| Pi | REST API | Why not MCP yet |
| A terminal, script or CI job | REST API | API tokens |
What each route can do
| Step | REST API | MCP |
|---|---|---|
| Create an account | POST /api/auth/sign-up/email |
In the browser, when the client opens the sign-in page |
| Create an organization | POST /api/auth/organization/create |
In the browser, at /organization-setup |
| Invite to the organization | POST /organization/invitations |
Not available |
| Invite to a project | POST /projects/{projectId}/invitations |
invite_project_member |
| Create a client | POST /clients |
create_client |
| Create a project | POST /projects |
create_project |
| Create a SOW | POST /projects/{id}/sows |
create_sow |
| Add task items | POST /task-items |
create_task_item |
| Add acceptance criteria | POST /task-items/{itemId}/criteria |
create_acceptance_criterion |
| Add tests | POST /criteria/{criterionId}/tests |
create_test |
| Produce the ATP | GET /api/sow/{sowId}/export, as Markdown or PDF |
get_acceptance_test_plan, as Markdown |
Every REST operation is in the API reference. Every MCP tool is in the tool catalog.
Hand it to your agent
Paste this into Claude Code, Codex, Cursor or Pi, and fill in the details:
Read https://docs.testandaccept.com/agents/journey/index.md and follow it to set
up this work in Test And Accept.
Client: <company name>
Project: <project name>
Work to deliver: <what is being built, or a path to the brief>
People to invite: <name, email and access level, or none>
If I'm already signed in to Tanda over MCP, use MCP. Otherwise use the REST route.
Ask me for my account details rather than inventing them, and never print my
password or API token. Confirm the invitations with me before sending them. When
you finish, give me the project ID, SOW ID, the ATP, and any criteria with no test.Every page on this site has a Markdown version at index.md, and /llms.txt lists them all.
Keep your credentials safe
- An API token acts as you, with your access, in one organization. It has no narrower scopes. Treat it like a password.
- Keep tokens in your secrets manager or an environment variable, not in a repository or a shared agent prompt.
- Text an agent reads can try to give it instructions, including text in a SOW or a client’s brief. Have it check with you before it invites anyone.