Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Inspect callable tools, capabilities, and parameters exposed to AI agents by Backengine Mcp.
list_projectsList customers and prospects; filter by name, type, etc.
get_projectRetrieve a customer or prospect, optionally with its overview.
get_project_overviewPre-computed rolling 12-week summary for a customer or prospect.
list_signalsList signals (categorized moments); filter by project, role, and time.
find_similar_signalsSemantic search across signals from a natural-language query.
list_sourcesList sources β transcripts, emails, Slack threads, and tickets.
The customer-context layer for your revenue team β available to Claude and any MCP client.
BackEngine is a multi-tenant SaaS platform that ingests all of an organization's customer and prospect communications β Slack threads, emails, call and meeting transcripts, and support tickets β and distills them into structured, queryable context. Raw conversations are processed into signals (categorized, attributed moments), sources (the underlying transcripts, emails, and tickets), and rolling project overviews, all isolated per tenant and scoped by role and access controls. The MCP server exposes this layer over the Model Context Protocol, so an LLM client can query customer signals, reconstruct context, prep for meetings, surface at-risk accounts, and draft grounded outreach from real conversation history β without leaving the chat.
The server is remote and speaks streamable HTTP at https://backengine-prod.backengine.ai/mcp. You'll
need a BackEngine account; the server authenticates your session on connect.
For clients that don't yet support remote servers directly, proxy through
mcp-remote:
The core tools for querying customer and prospect context are listed below. The exact tool set is resolved per connection β additional tools (creating and updating records, and integration-specific actions for Jira, Zendesk, HubSpot, Salesforce, and Slack) become available based on your permissions and which integrations your workspace has connected.
| Tool | Description |
|---|---|
list_projects | List customers and prospects; filter by name, type, etc. |
get_project | Retrieve a customer or prospect, optionally with its overview. |
get_project_overview | Pre-computed rolling 12-week summary for a customer or prospect. |
list_signals | List signals (categorized moments); filter by project, role, and time. |
find_similar_signals | Semantic search across signals from a natural-language query. |
list_sources | List sources β transcripts, emails, Slack threads, and tickets. |
get_source | Retrieve a source's content (summary, verbatim, or metadata only). |
list_roles | List the perspective lenses (e.g. product, sales, CS) used to filter signals. |
find_contacts | Find contacts by name, email, job title, or project. |
list_signal_speakers | List who has been speaking across signals. |
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/backengine-mcp)<a href="https://allmcps.com/mcp/backengine-mcp"><img src="https://allmcps.com/api/badge/backengine-mcp?style=directory" alt="Backengine Mcp on AllMCPs" /></a>