Backengine Mcp

Overview

From the repository's own README, as read at the audited commit.

<p>  <img src="assets/logo.png" alt="BackEngine" width="128" height="128"></p><h1>BackEngine MCP Server</h1><p>  The customer-context layer for your revenue team — available to Claude and any MCP client.</p>## What is BackEngine?BackEngine is a multi-tenant SaaS platform that ingests all of an organization's customerand prospect communications — Slack threads, emails, call and meeting transcripts, and supporttickets — and distills them into structured, queryable context. Raw conversations are processedinto **signals** (categorized, attributed moments), **sources** (the underlying transcripts,emails, and tickets), and rolling **project overviews**, all isolated per tenant and scoped byrole and access controls. The MCP server exposes this layer over the[Model Context Protocol](https://modelcontextprotocol.io), so an LLM client can query customersignals, reconstruct context, prep for meetings, surface at-risk accounts, and draft groundedoutreach from real conversation history — without leaving the chat.## ConnectingThe server is remote and speaks streamable HTTP at **`https://backengine-prod.backengine.ai/mcp`**. You'llneed 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 bridgeFor clients that don't yet support remote servers directly, proxy through[`mcp-remote`](https://www.npmjs.com/package/mcp-remote):```json{  "mcpServers": {    "backengine": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://backengine-prod.backengine.ai/mcp"]    }  }}```## ToolsThe core tools for querying customer and prospect context are listed below. The exact tool setis resolved per connection — additional tools (creating and updating records, andintegration-specific actions for Jira, Zendesk, HubSpot, Salesforce, and Slack) become availab

Details

Source

BackEngine-ai/backengine-mcp

Transports

streamable-http

Tools

Registered at runtime; the list could not be read from source.

Stars

1 · pushed 64d ago

Trust audit

Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (3)

streamable-http

Gates applied: no_behavioural_pass, no_license.

Audited 2026-09-13 · audit v0.4.0 · source sha 292d13aec8ee · full audit: observations/trust-audit/mcp-server/backengine-ai__backengine-mcp.json · Report an issue or request a re-scan

Audit history

Also audited

Servers with a similar trust profile.

Questions