Re:amaze MCP server
38 operations0 webhooks
Customer support inbox for Re:amaze - read and reply to conversations, manage contacts, identities and notes, publish help articles, and pull the volume, response time, tag and channel reports.
Try Re:amaze with your agent
Connect Re:amaze, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Re:amaze on my account, then run one read-only example and show me the result.
Re:amaze tools and triggers
Tools are what your agent can do in Re:amaze through Corsair's MCP server. Triggers are the Re:amaze events a routine can start from.
Reports
- Channel SummaryRead-only
Per-channel response counts, response time, satisfaction and thread size
reports.channelSummary
- Response TimeRead-only
Daily first-response time in seconds, with averages and ratios
reports.responseTime
- StaffRead-only
Per-staff response counts, response time and appreciations
reports.staff
- TagsRead-only
Tag usage counts over a date range
reports.tags
- VolumeRead-only
Daily conversation volume over a date range
reports.volume
Articles
- CreateWrite
Create a help center article under a topic
articles.create
- GetRead-only
Read one help center article by slug
articles.get
- ListRead-only
List help center articles, filtered by status or search text
articles.list
- UpdateWrite
Change an article title, body, status or topic
articles.update
Conversations
- CreateWrite
Create a conversation on behalf of a customer, with its first message
conversations.create
- GetRead-only
Read one conversation by slug, reference id, or origin id within a channel
conversations.get
- ListRead-only
List conversations, filtered by status, assignee, tag, channel, origin or date
conversations.list
- UpdateWrite
Change a conversation status, tags, assignee, data attributes or channel
conversations.update
Incidents
- CreateWrite
Create a status page incident with its first update, which shows on the public status page
incidents.create
- GetRead-only
Read one status page incident by id
incidents.get
- ListRead-only
List status page incidents
incidents.list
- UpdateWrite
Change a status page incident and append an update, which shows on the public status page
incidents.update
Notes
- CreateWrite
Add a note to one contact
notes.create
- DeleteDestructive
Delete one contact note. Re:amaze keeps no undo and the note text is not returned anywhere afterwards
notes.delete
- ListRead-only
List the notes on one contact
notes.list
- UpdateWrite
Replace the text of one contact note
notes.update
Response Templates
- CreateWrite
Create a response template
responseTemplates.create
- GetRead-only
Read one response template by id
responseTemplates.get
- ListRead-only
List response templates, filtered by search text
responseTemplates.list
- UpdateWrite
Change a response template name or body
responseTemplates.update
Contacts
- CreateWrite
Create a contact for the account
contacts.create
- ListRead-only
List contacts, filtered by search text, type or data attributes
contacts.list
- UpdateWrite
Change a contact name, friendly name, avatar or data attributes, and append notes
contacts.update
Channels
- GetRead-only
Read one channel by slug
channels.get
- ListRead-only
List the brand channels, optionally by type
channels.list
Identities
- CreateWrite
Attach an identity to a contact. An identity already on another contact is moved here with its messages
identities.create
- ListRead-only
List the emails, handles and phone numbers attached to a contact
identities.list
Messages
- CreateWrite
Send a reply in a conversation. It goes out to the real customer and the other participants unless suppress_notifications is set. visibility 1 posts an internal note only staff see
messages.create
- ListRead-only
List messages across the brand, filtered by sender, tag, channel or date
messages.list
Staff
- CreateWrite
Create a staff user, which counts toward the monthly subscription. No invite email is sent
staff.create
- ListRead-only
List staff users, oldest first
staff.list
Satisfaction
- ListRead-only
List satisfaction survey ratings, filtered by brand, rating or date
satisfaction.list
Systems
- ListRead-only
List the status page systems and their current status
systems.list
Connect Re:amaze to Claude, ChatGPT or Cursor
- 1
Connect Re:amaze in Corsair
Add your Re:amaze API key once in Corsair. Corsair stores the credential encrypted and makes the Re:amaze API calls for your agent, so it never goes into a prompt or a config file. Connect Re:amaze
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Re:amaze. On a ChatGPT personal plan, connect Re:amaze here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Re:amaze's read and write operations run right away and its 1 destructive operation waits for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/reamaze, add the Re:amaze plugin, and connect with an API key. Then call methods like corsair.reamaze.api.articles.create() from your app. Corsair keeps each tenant isolated.
Yes. Re:amaze requires an API key from your Re:amaze account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Re:amaze, GitHub, Notion, Stripe, and the rest. Trigger Re:amaze from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for customer support inbox for Re:amaze - read and reply to conversations, manage contacts, identities and notes, publish help articles, and pull the volume, response time, tag and channel reports. Common builds include sync jobs, admin tooling, and agents that call Re:amaze APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Re:amaze API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/reamaze in the open repo. When Re:amaze ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Re:amaze data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Re:amaze data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Re:amaze on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 1 destructive Re:amaze operation. You can change a link's mode at hub.corsair.dev/me.