// Platform — AI agents (MCP)
Your agents, briefed. Over MCP.
Claude Code, Cursor or any MCP client pulls the real captured context — console errors, failed requests, user steps, suspected source — instead of a one-line description.
Mint a scoped token
rbk_ tokens are minted in the widget with explicit scopes, shown once and stored only as a hash.
Connect the agent
@rebasedotdev/mcp runs locally over stdio — add it to your agent's MCP config and it's connected.
It acts in the thread
An agent's comment or status change lands in the same in-page thread the reporter is watching.
// Five tools, full context
The agent reads what the widget saw.
list_tickets, search_tickets, get_ticket, add_comment and update_ticket_status — enough to find, understand, discuss and resolve without leaving the editor.
- get_ticket returns the full capture — screenshot optional, up to 10 MB
- Semantic search: 'checkout is broken' finds the 500 on /orders
- Local over stdio — the only network traffic is HTTPS to the Rebase API
{ "mcpServers": { "rebase": { "command": "npx", "args": ["-y", "@rebasedotdev/mcp"] } }}// Scoped, hashed, revocable
Read-only agents, first-class.
Scope a token to tickets:read for observer agents — write scopes are opt-in. Tokens show their last-used time, expire after a year by default, and revoke with one click.
- Three scopes: tickets:read, tickets:write, comments:write
- Shown once, stored only as a SHA-256 hash
- Purpose-built rate limits per token
API tokensrbk_…claude-code — read-only agent
revoke any time
// The details
Built for coding agents. One clean surface.
- Five MCP tools: list, search, get, comment, update status
- Semantic search by meaning — scored, over the last 90 days
- Search, duplicate matching and embeddings cost zero credits
- Agent replies land in the thread your team is watching
- rbk_ tokens with explicit scopes and 365-day default expiry
- 120 reads / 30 writes / 30 searches per minute, per token
- The MCP server runs on your machine — stdio in, HTTPS out
Frequently asked questions
Anything that speaks MCP — Claude Code and Cursor work out of the box via @rebasedotdev/mcp, and any other MCP client can connect the same way.
Find tickets, search them semantically, pull the full capture — optionally with the screenshot as an image — add comments and update status. Its replies land in the same in-page thread the reporter is watching.
No. It runs locally over stdio on the developer's machine; the only network traffic is HTTPS to the Rebase API.
No. Semantic search is free and uncapped by credits — credits are only spent when the AI triages a ticket.
// Keep exploring
The rest of the platform. It all works together.
Capture
Click to report — console, network, steps & a screenshot.
Triage & AI
Summary, severity & the suspected file — evidence-linked.
Detected issues
Uncaught errors from real sessions, queued for review.
Collaboration
Pins on the live page — threads, mentions & roles.
Issue-tracker sync
Files into GitHub, Linear, Jira & Asana. Two-way status.
Team & notifications
Invites, roles, unlimited users — mentions instant, the rest digested.
Privacy & security
Masked by default, scrubbed twice, isolated per tenant.
Start shipping feedback faster.
Start your 7-day free trial.