About Backengine Mcp
BackEngine Mcp exposes an organization's customer and prospect communications as structured, queryable context for revenue teams. It helps MCP clients retrieve conversation signals and sources, prepare for meetings, identify account risks, and draft context-grounded outreach.
Key features
- 01Query categorized conversation signals
- 02Search signals semantically
- 03Retrieve transcripts, emails, and tickets
- 04View rolling customer overviews
- 05Filter context by role and access
- 06Find contacts by project or details
Use cases
- 01Prepare for a customer meeting
- 02Review recent account signals
- 03Surface potentially at-risk accounts
- 04Draft outreach using conversation history
MCP support
The remote MCP server uses streamable HTTP and exposes BackEngine's customer-context tools to MCP clients. Available tools vary by permissions and connected integrations, with some integration-specific actions also available.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://backengine-prod.backengine.ai/mcpclaude mcp add --transport http backengine https://backengine-prod.backengine.ai/mcp{"mcpServers":{"backengine":{"type":"http","url":"https://backengine-prod.backengine.ai/mcp"}}}Open in Cursor{"servers":{"backengine":{"type":"http","url":"https://backengine-prod.backengine.ai/mcp"}}}Open in VS Code{"mcpServers":{"backengine":{"type":"http","url":"https://backengine-prod.backengine.ai/mcp"}}}{"mcpServers":{"backengine":{"serverUrl":"https://backengine-prod.backengine.ai/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project README
BackEngine MCP Server
The customer-context layer for your revenue team — available to Claude and any MCP client.
What is BackEngine?
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.
Connecting
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.
Clients with native remote MCP support
{
"mcpServers": {
"backengine": {
"type": "streamable-http",
"url": "https://backengine-prod.backengine.ai/mcp"
}
}
}
Clients that require a stdio bridge
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"]
}
}
}
Tools
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. |
Links
- Website: https://backengine.ai
- MCP endpoint: https://backengine-prod.backengine.ai/mcp
- Model Context Protocol: https://modelcontextprotocol.io
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.