Discount code accepted but total unchanged
/checkout?step=payment
High Medium AR
checkout
Everything the panel does, your AI agent can do too
Notarus ships an MCP (Model Context Protocol) server with 100% panel parity. Triage, reply, move tickets and open review sessions from Claude, Cursor or your own agent.
Included on Free and Pro · one endpoint, one token
The Notarus MCP server registers nineteen tools, by the panel surface each one drives. Tickets: list_tickets, get_ticket, create_ticket, move_ticket, assign_ticket, comment_ticket. Sessions: list_sessions, get_session, get_recording, search_logs, get_errors. Board: list_ticket_statuses, reorder_ticket_statuses, ticket_stats, get_insights. Reporter portal: create_reporter_portal_link, render_reply_template, get_client_portal, set_client_portal. An agent connected to it lists tickets by status, reads a session recording, searches captured logs and moves a ticket between statuses, without anyone opening the panel.
Nineteen of the tools the server registers, named by the surface each one drives.
get_documentation returns the rest as a manual your agent can read.
How it works
1
Create a personal access token
Tokens are minted in Personal settings → API & MCP and start with pat_. The server stores only a SHA-256 digest, and the token carries your own role on each project.
2
Connect the endpoint
Point any MCP client at https://app.notarus.ai/mcp with the token in an Authorization header. The transport is stateless, so there is no session to keep alive.
3
Call the tools
Triage, reply, move tickets, run surveys, read sessions and open review sessions — the same operations, under the same permission checks as the panel.
claude mcp add -t http notarus \
https://app.notarus.ai/mcp \
-H "Authorization: Bearer pat_…"Parity is a rule, not a roadmap
The menu on a card and the tool an agent calls are the same operation: one write, one activity entry, the same permission check. That is why the tool list tracks the product instead of trailing a release behind it.
Every call answers with the whole record it touched, so an agent never has to read a second tool to find out what it just did.
Panel
WIP 1
QA 2
Survey text overflows on mobile
/pricing
Medium AR
surveys
Widget launcher covers the cookie banner
/
Low DM
widget
MCP
> move_ticket ticket:"NT-248" status:"qa" { "ticket": { "id": "8f3a1d54-2b17-4c9e-9a20-6d5e0b71c433", "shortId": "NT-248", "type": "bug", "title": "Discount code accepted but total unchanged", "status": "qa", "priority": "high", "severity": "medium", "labels": [ "checkout" ], "rating": null, "assurance": "verified", "commentExcerpt": "The code applies but the order total never changes.", "pageUrl": "https://shop.example.com/checkout?step=payment", "assigneeId": "1c47b0e2-9d3f-4a68-8b51-72c0ad9e4f16", "hasScreenshot": true, "hasVideo": true, "dueAt": null, "archivedAt": null, "createdAt": "2026-08-26T09:12:44.118Z" } }
A token, not an integration project
There is no app to register and no bridge process to run: a name, a button, and a secret you copy once. The server keeps only a SHA-256 digest of it, so the plaintext exists on that screen and nowhere else.
The token carries your own role on each project and every tool is checked against it — a viewer's token reads everything and moves nothing.
API & MCP
Create personal tokens for MCP clients and API automation.
Your MCP tokens
Tokens are personal: every MCP call authenticates as you, with your roles. Any role can create one.
pat_9f2c41ab… “Claude Code” never used Revoke
pat_4d7e0c33… “Cursor” last used 8/26/2026, 9:41:12 AM Revoke
pat_b1a58e70… “Release bot” last used 8/21/2026, 6:07:55 PM Revoke
pat_9f2c41ab7d5e2c6408b31af97e0d54c2a6b8f3d1 Copy — shown only once
Token name Create token
100% panel parity
The panel's own sections, each with its tools. There is no capability that exists only behind the interface.
- Projects
- Board & pipeline
- Tickets
- Reply templates
- Sessions, logs & performance
- Surveys
- Insights & AI enrichment
- Client portal
- Review mode
- Members & invites
- Notifications
- Integrations
- Widget, domains & masking
- Single sign-on
- Billing & plans
- Exports & audit log
Exact behaviour
- Endpoint
- POST /mcp — GET and DELETE answer 405
- Transport
- Streamable HTTP, stateless, JSON responses
- Auth
- Authorization: Bearer pat_… — a personal access token, per user
- Unauthorized
- 401 with JSON-RPC −32001 and a WWW-Authenticate: Bearer header
- Rate limit
- 240 calls a minute per token; 429 with JSON-RPC −32000
- Permissions
- The token's own role on each project, checked per tool
- Parity
- Every panel capability has an MCP tool
- Plan
- Included on Free and Pro
Questions developers ask first
Which tools exist?
Ask the server: it answers tools/list on connect, and get_documentation returns this product's entire manual as text an agent can read. Parity is a rule the product is built under — a feature ships with its MCP tool or it is not finished — so the list tracks the panel rather than trailing a release behind it.
Can I use Notarus without ever opening the panel?
Almost. The one thing that starts in the panel is the token itself, because a token is what authenticates the call that would create it. After that, projects, tickets, replies, surveys, members, integrations and billing all have tools.
How do I connect from claude.ai?
You do not, yet. Claude Code and the Claude API MCP connector take the endpoint and a token directly. claude.ai custom connectors attach only servers with no auth or with OAuth, and cannot send the bearer header this endpoint needs.
What does a failed call look like?
A bad credential is an HTTP 401 with a JSON-RPC error. Everything else — a missing ticket, a role that is not allowed, a value that does not validate — comes back as a successful tool call with isError: true and a JSON body naming the reason, so an agent can read it and react instead of crashing.
Give your agent the same access your team has.
The MCP server is included on the Free plan.
Start free Free plan · No credit card