backengine-mcp
Surface customer context from Slack, email, transcripts and tickets.
View on GitHub Updated 2026-06-29
What is the backengine-mcp MCP server?
By indexing messages, threads, and ticket histories, backengine-mcp returns concise, relevant snippets that mention a person or company. This lets agents quickly understand prior conversations, open issues, or recent sentiment without switching tools.
The integration focuses on read-only access to communication channels and ticketing systems, keeping all data retrieval inside the MCP protocol layer.
Install & connect
Add this to your MCP client config. Pick your client below and copy.
{
"mcpServers": {
"backengine-mcp": {
"url": "https://mcp.backengine.ai/mcp"
}
}
}Example prompts
Once connected, try asking your AI client:
“What has Acme Corp discussed with us on Slack in the last month?
“Show me the latest emails and tickets for [email protected]
“Summarize the call transcript and open issues for prospect BetaCo
“Find any recent mentions of renewal or churn risk for our top accounts
Security & permissions
Requires streamable-http access and environment variables for Slack, email, and ticketing API credentials; only reads conversation and ticket data.
What you can do with backengine-mcp
Pre-meeting briefing
Fetch recent Slack threads and email threads for a prospect before a sales call.
Support ticket context
Pull transcript and ticket history for a customer who just opened a new issue.
Account research
Surface mentions of a target company across all connected communication channels.
How to use backengine-mcp
- 1Clone the backengine-mcp repository and install dependencies.
- 2Create a .env file with API tokens for Slack, email provider, and ticketing system.
- 3Start the server with the streamable-http transport.
- 4Add the server URL to your MCP client configuration.
- 5Test connectivity by asking the client to retrieve context for a known contact.
backengine-mcp: pros & cons
Pros
- +Works in any MCP-compatible client without custom plugins
- +Aggregates context from four common communication sources
- +Lightweight read-only design reduces data exposure
- +Simple streamable-http deployment for remote use
Cons
- –No tools are publicly documented in the README
- –Requires separate API keys for each connected service
- –Context quality depends on the completeness of connected data sources
Did you find this helpful?
Frequently asked questions
No, it performs on-demand queries against the connected services and returns results in real time.
User reviews
Verified reviews from the community shape this listing's rating.
Loading reviews…
Similar MCP servers
Other communication connectors worth a look.
