AoTwin

File and follow tickets from your AI assistant.

Connect AoTwin to the AI assistant you already use. It works through MCP, a standard way for assistants to use other tools, and you set it up once.

  • Ask for a ticket in plain words.

  • Find, read and update tickets without leaving the chat.

  • Filing never starts AoTwin. Assigning does.

Connects to Claude, Claude Code and Cursor. Sign in once and you’re connected. There’s no key to copy.

Your MCP address

https://app.aotwin.io/mcp

Your AI assistant

  1. Maya

    File a ticket in AoTwin: the Export button on the reports page does nothing in Safari. Assign it to me.

  2. Assistant

    Done. I filed WEB-232 and assigned it to you.

In AoTwin

Export button does nothing in Safari

WEB-232

Status
To do
Assignee
Maya
From
An AI assistant
An illustrative example.

Connect in a minute.

One address for every assistant: app.aotwin.io/mcp.

  • claude.ai and the Claude apps

    Go to Customize → Connectors, choose Add custom connector, paste this address, then sign in.

    https://app.aotwin.io/mcp

    On a Team or Enterprise plan, an owner adds it once under Organization settings → Connectors. Then each person connects from Customize → Connectors with their own account.

  • Claude Code

    Run this once in a terminal. Then run /mcp in Claude Code and sign in.

    claude mcp add --transport http aotwin https://app.aotwin.io/mcp
  • Cursor

    Add it in one click, then sign in when Cursor asks.

    Add to Cursor

    Or paste this into your mcp.json.

    {"mcpServers":{"aotwin":{"url":"https://app.aotwin.io/mcp"}}}
  • VS Code

    Run MCP: Add Server from the Command Palette, choose HTTP and paste the address. Then sign in when VS Code asks.

    Or paste this into .vscode/mcp.json.

    {"servers":{"aotwin":{"type":"http","url":"https://app.aotwin.io/mcp"}}}
  • Codex

    Run these once in a terminal, then sign in in the browser.

    codex mcp add aotwin --url https://app.aotwin.io/mcp
    codex mcp login aotwin
  • Zed

    Open Settings → AI → MCP Servers, choose Add Server, then Add Remote Server, and sign in when Zed asks.

    Or paste this into your settings file.

    {"context_servers":{"aotwin":{"url":"https://app.aotwin.io/mcp"}}}
  • Other assistants

    Most take the address directly. If yours only runs local commands, give it this one instead. It needs Node.js.

    npx -y mcp-remote https://app.aotwin.io/mcp

What your assistant can do.

  • File a ticket

    Describe it in plain words. The assistant fills in the title, the details and the project.

  • Find and read tickets

    Ask what’s assigned to you, what’s waiting on review, or what a ticket says.

  • Update them

    Comment, change the status, assign, reopen or close, without leaving the chat.

  • Hand one to AoTwin

    Only when you ask. Assigning a ticket to AoTwin is what starts the work.

Things to ask it.

  • “What’s waiting on me in AoTwin?”

    Reads your inbox: questions from AoTwin and work ready for you to review.

  • “File a ticket: the footer links overlap on phones.”

    Files it for nobody. If someone already filed something similar, you get that ticket back instead.

  • “Turn these meeting notes into tickets. Show me the list before you file anything.”

    You check the list first, then the assistant files what you keep.

  • “What’s in review in WEB, and who is it assigned to?”

    Filters by project and status, and lists what it finds with a link to each ticket.

  • “Read AO-123 and tell me what AoTwin changed.”

    Sums up the ticket and the work done on it, in plain words.

  • “Hand AO-123 to AoTwin.”

    The only one here that starts AoTwin, and it uses credits.

The tools it gets.

A read-only connection gets only the first group.

Read

  • whoamiSays which person and workspace the connection acts as.
  • list_requestsFinds tickets by text, project, assignee or status.
  • get_requestReads one ticket, with what AoTwin changed and the activity so far.
  • inboxLists what needs you: questions from AoTwin and work ready to review.
  • list_projectsLists the workspace’s projects and their keys.
  • list_peopleLists the people in the workspace.

Change

  • create_requestFiles a ticket. This never starts AoTwin.
  • update_requestEdits a ticket’s title, description or page.
  • commentAdds a comment as you. It can answer a question from AoTwin.
  • assignAssigns a ticket. Assigning to AoTwin starts the work and uses credits.
  • set_statusMoves a ticket to another status.
  • reopenReopens a ticket that’s done or canceled.
  • close_requestCancels a ticket, and stops AoTwin if it’s working on it.

Questions about MCP.

  • What is MCP?

    A standard way for AI assistants to use other tools. AoTwin speaks it, so the assistant you already use can work with your tickets.

  • Is there a key to copy?

    No. Sign in to AoTwin once when the assistant asks, and it acts as you, in your workspace.

  • Which plans include it?

    Every plan, Free included.

  • Will it start AoTwin by itself?

    No. Filing and editing a ticket never start it. Only assigning a ticket to AoTwin does, and that uses credits.

  • Can I connect it read-only?

    Yes, if your assistant lets you choose scopes: ask only for read when you sign in. It then gets just the tools that read, and your account shows the connection as read only.

  • How do I use another workspace?

    Each connection acts in one workspace, which you pick when you sign in. Remove AoTwin from your assistant and connect again to pick a different one.

  • How do I disconnect it?

    Open your account in AoTwin, find Connected AI tools and choose Disconnect. It stops working straight away. Open your account

  • It won’t connect. What do I do?

    Remove AoTwin from your assistant, add it again and sign in once more. That doesn’t touch your tickets. If you use mcp-remote, also delete the ~/.mcp-auth folder, which holds its saved sign-in, and update Node.js. Still stuck? Write to us below.

Tell us about your backlog.

Ask a question, ask what it would cost for your team, or describe the tickets you’d hand over. We reply by email.

Thanks. Your message is sent, and we’ll reply by email.