Backengine Mcp

ai.backenginePublished by backengine.aiOfficial publisherv8.1.1Updated Oct 24, 2026

Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote BackEngine MCP server that lets an assistant query customer and prospect context distilled from Slack, email, transcripts and tickets.

What you can do
  • List and retrieve customers and prospects, including their rolling 12-week overviews
  • List and semantically search signals (categorized moments) filtered by project, role and time
  • List and read sources such as transcripts, emails, Slack threads and tickets, as summary, verbatim or metadata
  • Find contacts by name, email, job title or project, and list roles and signal speakers
  • Depending on permissions and connected integrations, additional tools for creating and updating records and for Jira, Zendesk, HubSpot, Salesforce and Slack actions
When to use it
Useful for revenue, sales and customer-success work where an assistant should answer questions from real conversation history: prepping for meetings, reconstructing account context, spotting at-risk accounts, or drafting grounded outreach.
Requirements
A remote streamable HTTP endpoint; a BackEngine account is required and the server authenticates the session on connect via OAuth. Clients without native remote MCP support need a stdio bridge such as mcp-remote run through npx (Node.js).
Before you install
The server holds customer and prospect communications, so access is scoped by role and tenant access controls. The available tool set depends on permissions and connected integrations; some tools can create and update records or act in Jira, Zendesk, HubSpot, Salesforce and Slack, which changes data in those systems.

Installation

In SourceWeft

  1. Open Backengine Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.backengine%2Fbackengine-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "backengine": {
      "type": "http",
      "url": "https://backengine-prod.backengine.ai/mcp"
    }
  }
}

README

[BackEngine]

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

json
{  "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:

json
{  "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.

ToolDescription
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.
get_sourceRetrieve a source's content (summary, verbatim, or metadata only).
list_rolesList the perspective lenses (e.g. product, sales, CS) used to filter signals.
find_contactsFind contacts by name, email, job title, or project.
list_signal_speakersList who has been speaking across signals.

Links

Source: README.md at commit b0bfc6a

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v8.1.1LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.