ai.backengine/backengine-mcp
Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http backengine-mcp 'https://backengine-prod.backengine.ai/mcp'{
"mcpServers": {
"backengine-mcp": {
"type": "http",
"url": "https://backengine-prod.backengine.ai/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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
Frequently asked questions
What is ai.backengine/backengine-mcp?
Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.
How do I install ai.backengine/backengine-mcp?
It runs as a remote server. In Claude Code: claude mcp add --transport http backengine-mcp 'https://backengine-prod.backengine.ai/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does ai.backengine/backengine-mcp need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is ai.backengine/backengine-mcp open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains ai.backengine/backengine-mcp?
It is published by BackEngine-ai. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.