Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Remote HTTPChoose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Capabilities & Tool Schemas (10)
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.
Documentation Overview
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
Clients that require a stdio bridge
For clients that don't yet support remote servers directly, proxy through
mcp-remote:
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
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars
1
Stargazers on the source repository.
Last commit
2mo ago
Most recent push to the default branch.
Tools exposed
10
Callable tools this server registers over MCP.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Backengine MCP
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/backengine-mcp)HTML Embed
<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>Technical Specs & Signals
CategoryCommunication
11/11 checks healthy over the last 45d
51Quality signal: Good · 51/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools25/30
Adoption & activity3/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.