Bring your customer memory into Claude and ChatGPT. Hyperengage exposes accounts, usage, conversations, signals, and commitments as 19 typed MCP tools — with secure OAuth sign-in, and every call running on your own permissions.
Your AI assistants
Claude
claude.ai · Desktop
ChatGPT
Developer mode
Claude Code
Coming soon
Cursor
Coming soon
More MCP clients coming
Hyperengage MCP server
api.hyperengage.io/mcp
15
read tools
1
intelligence
3
write tools
Customer Memory Graph
One reconciled record per customer
19
MCP tools
6
ready-made prompts
OAuth 2.1
sign-in, no API keys
2
assistants today: Claude & ChatGPT
MCP in your assistant
Your assistant picks the right Hyperengage tools, pulls live customer state, and reasons over it — then writes its work back as a task, note, or brief your team will actually see.
Two renewals need attention:
Northwind Labs
Renews in 34 days. Weekly active users down 38% since August; two open priority tickets; their champion stopped replying.
Fabrikam Health
Renews in 51 days. Promised SSO rollout is 3 weeks late; exec sponsor asked about contract terms on the last call.
Want me to create follow-up tasks for the owners?
The tool catalog
Typed, documented tools your assistant discovers automatically. Read tools are marked read-only, so clients know which calls change nothing.
Find any customer and pull the full record.
whoamiWho is connected, and to which workspace.readsearchFind accounts, contacts, and records across the workspace.readfetchRetrieve a search result in full.readget_accountEverything about one account: health, owners, traits, context.readget_contactA contact's profile, role, and engagement.readquery_recordsFilter records by fields, dates, and conditions.readWhat customers actually do — and what they said.
get_usage_trendsProduct usage trends for an account over time.readget_trait_historyHow a trait (seats, plan, health) changed over time.readsearch_conversationsSemantic search across emails, meetings, and threads.readget_account_timelineA chronological timeline of everything on an account.readThe reasoning layer — risks, commitments, and signals.
get_insightsRisks and opportunities across the book, weighted by ARR.readget_commitmentsPromises made to and by customers, across conversations.readlist_signalsSignals firing on accounts, with the evidence behind them.readget_business_contextYour company's playbooks, ICP, and definitions.readget_documentRead a saved brief, plan, or document.readHand a hard question to Hyperengage's own agents.
ask_hyperengageRuns Hyperengage's skills agent with your playbooks to answer multi-step questions.intelligenceAgents leave their work where your team will see it.
save_documentSave a brief, plan, or summary to the account.writecreate_taskCreate a follow-up task for an owner.writelog_noteLog a note on an account or contact.writeReady-made prompts
Six MCP prompts package our best post-sales workflows. Pick one in your assistant and it runs the right tools for you.
What needs your attention today, across your whole book.
/daily_focusA complete, evidence-backed brief on one account.
/account_briefHealth, open issues, and commitments before a call.
/meeting_prepRisk, value delivered, and a plan for an upcoming renewal.
/renewal_reviewA quarterly business review drafted from real account data.
/qbrWhat customers are saying, grouped into themes.
/voice_of_customerSecure authentication
Standard OAuth 2.1 — no API keys pasted into chat windows. You choose exactly what each assistant is allowed to do.
Paste one URL into Claude or ChatGPT. No API keys to create, copy, or rotate.
Standard OAuth 2.1 sign-in with your Hyperengage account and workspace.
Grant read, intelligence, and write separately. Leave write off if you only want answers.
Tools see exactly what you can see in Hyperengage — nothing more.
Your assistant wants to access Hyperengage
Workspace: Acme Customer Success
Read your customer data
hyperengage:read
Ask Hyperengage agents
hyperengage:intelligence
Save documents, tasks, and notes
hyperengage:write
Read
hyperengage:readRead accounts, contacts, usage, conversations, and signals you already have access to.
Intelligence
hyperengage:intelligenceLet the client run ask_hyperengage, which uses AI credits.
Write
hyperengage:writeLet the client save documents, create tasks, and log notes.
Every call goes through the same permission checks as the Hyperengage app. Assistants see what you can see — nothing more.
Your workspace comes from your sign-in. No tool accepts a workspace ID, so an assistant can't reach into another one.
Email and meeting search respects per-mailbox access, so shared tools don't expose conversations you weren't part of.
Read, intelligence, and write are separate permissions you approve at sign-in — and can revoke at any time.
Every write and intelligence call is recorded: who, which tool, and when.
Per-user limits keep every assistant fast and fair across your team.
Errors come back as a reference ID, never a stack trace or internal detail.
Model Context Protocol over streamable HTTP, with OAuth 2.1 discovery. No proprietary SDK required.
Connect
The same connector URL works in every supported assistant.
https://api.hyperengage.io/mcpHyperengage's Renewal, Churn-Risk, Expansion, and Account Prep agents read the same Customer Memory Graph. Use MCP to bring it into your own assistant — or let our agents and engineers do the work for you.
FAQ
It's one API for your post-sales agents. Hyperengage exposes your customer memory — accounts, contacts, usage, conversations, signals, and commitments — as 19 typed tools and 6 ready-made prompts over the Model Context Protocol (MCP), so assistants like Claude and ChatGPT can read live customer state and write their work back.
Claude (claude.ai and Claude Desktop) and ChatGPT (via developer mode connectors) are supported today, both using the same connector URL. Claude Code and Cursor are coming next. Other clients that support remote MCP servers with OAuth may work, but aren't officially supported yet.
Standard OAuth 2.1. You add the connector URL, sign in with your Hyperengage account, choose your workspace, and approve the permissions the client is asking for. There are no API keys to copy or paste, and you can revoke access at any time.
No. Every tool call runs as you and goes through the same permission checks as the Hyperengage app, including per-email access controls on conversations. The workspace comes from your sign-in — no tool accepts a workspace ID from the client, so an assistant can't reach into another workspace.
Only if you grant the write scope. Write tools are limited to saving documents, creating tasks, and logging notes, and are clearly marked as write actions so your client can ask for confirmation. Every write and intelligence call is recorded in an audit log.
Calls are rate-limited per user to keep things fast and fair. ask_hyperengage runs Hyperengage's own agents and uses AI credits; all other read tools don't.
The Hyperengage MCP server is in beta. Tell us which assistant your team uses and what you want it to do — we'll get you connected.