Guide
Connect an AI assistant to Hookfire, so it can read your notifications and act on them, as you.
Hookfire runs an MCP server: a web address an AI assistant such as Claude or ChatGPT connects to. It is for organization admins. Once connected, the assistant can list the organizations where you are an admin, their integrations and your notifications, count the events that arrived, mark notifications read, acknowledge alerts, send test events and mute integrations. It signs in as you and does what an admin can do in the app, nothing more.
On Max It works in the organizations on the Max plan where you are an admin.
https://hookfire.app/mcp
Most clients sign in with your Hookfire account: you paste the server URL, a browser opens, you sign in and approve. Menu names in these apps change from time to time, so look for the nearest match if a step does not line up.
On Team and Enterprise plans, an owner adds the connector first under Admin settings > Connectors, then each member clicks Connect and signs in with their own Hookfire account. Remote servers are added this way, not in claude_desktop_config.json.
Add the server from your terminal:
claude mcp add --transport http hookfire https://hookfire.app/mcp
Then run /mcp inside Claude Code and choose to authenticate. A browser opens for you to sign in to Hookfire and approve.
Add this to ~/.cursor/mcp.json
(or .cursor/mcp.json
in a project):
{
"mcpServers": {
"hookfire": {
"url": "https://hookfire.app/mcp"
}
}
}
Cursor then offers to sign in. If its built-in browser does not load the sign-in page, copy the link into your normal browser.
Or add it to .vscode/mcp.json:
{
"servers": {
"hookfire": {
"type": "http",
"url": "https://hookfire.app/mcp"
}
}
}
A client that cannot sign in can use a personal token instead. Make one in Settings > MCP server. It is shown once, lasts 90 days and only works with the MCP server. The client sends it as a header:
Authorization: Bearer YOUR_TOKEN
For a client configured with JSON, that looks like this:
{
"mcpServers": {
"hookfire": {
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
},
"url": "https://hookfire.app/mcp"
}
}
}
These are the tools the server offers, read from the server itself. The assistant picks the ones it needs for what you ask.
list_organizations
Lists the organizations this account can work in: the ones on Max where it is an admin, with each one's id, name and plan. Call this first: most other tools take an organization id.
list_integrations
Lists an organization's integrations: the connected service, whether it is accepting webhooks, whether its notifications are muted, the events it notifies about with each event's urgency and whether it is paused, and the events that could be switched on.
list_notifications
Lists notifications in this account's inbox, newest first, one page at a time. Narrow it to one organization or integration, or to unread ones. Each notification is one event that arrived, with its title, text, urgency and whether it has been read or acknowledged.
get_notification
Gets one notification in full: its title, text, link, link buttons, the values Hookfire read from the payload (such as amount and customer email), and why it was not pushed if it was not.
event_counts
Counts the events an organization received over the last few days, per integration and event type, leaving out tests. Use it to answer questions like how many payments failed this week.
mark_notifications_read
Marks notifications in this account's inbox as read: the ones listed in ids, or every unread one in an organization. Reading a critical alert also acknowledges it, which stops its repeats.
acknowledge_notification
Acknowledges a critical alert in this account's inbox, so it stops repeating to this account. Others it was sent to answer their own.
send_test_event
Sends an integration's sample payload for one of its switched-on events, delivered exactly like a real one, marked as a test. Refused when the sample does not pass the event's own payload rules.
mute_integration
Mutes an integration's notifications for some hours, until unmuted, or unmutes it. A muted integration still records every event in the history; it only stops notifying.
Things you can ask, and the tools that answer them.
"How many payments failed this week?"
Counts the organization's events per integration and event type, up to 90 days back.
event_counts
"What was in the last Shopify order notification?"
Finds it in your inbox and opens it, with the values Hookfire read and its link, as the app shows it.
list_notificationsget_notification
"Acknowledge the critical Sentry alert."
Stops it repeating for you. Others it went to answer their own.
list_notificationsacknowledge_notification
"Mute Sentry for two hours."
Events are still recorded in the history, they just do not notify.
list_integrationsmute_integration
"Send a test charge.failed to the Stripe integration."
Delivered like a real event, marked as a test. The event has to be switched on.
list_integrationssend_test_event
"Mark everything in my organization as read."
Marks every unread notification of that organization as read, in your inbox.
list_organizationsmark_notifications_read
The server explains each refusal. Here is what the messages mean.
Still stuck? Contact support.