BackEngine MCP Server

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.

Related MCP server: Tribal

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.

Links

• Website: https://backengine.ai

• MCP endpoint: https://backengine-prod.backengine.ai/mcp

• Model Context Protocol: https://modelcontextprotocol.io