Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"backengine": {
"url": "https://backengine-prod.backengine.ai/mcp",
"type": "streamable-http"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The customer-context layer for your revenue team — available to Claude and any MCP client.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
One local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in.
MCP Security Weekly
Get CVE alerts and security updates for ai.backengine/backengine-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
{
"mcpServers": {
"backengine": {
"type": "streamable-http",
"url": "https://backengine-prod.backengine.ai/mcp"
}
}
}
For clients that don't yet support remote servers directly, proxy through
mcp-remote:
{
"mcpServers": {
"backengine": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://backengine-prod.backengine.ai/mcp"]
}
}
}
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. |