Governed AI Agents with Proof Receipts

Run AI agents against Evercore safely: MCP-compatible tools via POST /assistant/mcp, scoped API keys, human-in-the-loop approvals, and replayable console runs — every action produces a verifiable, tamper-proof receipt.

POST /assistant/mcp exposes tools/list and tools/call for allowlisted Evercore routes. API-key scopes, proof receipts, and replayable console workflow runs keep agents inside the same governed evidence stack as your teams.

Give agents the same governed API your teams already trust.

Evercore exposes MCP-shaped tools, API-key scopes, proof receipts, and replayable workflow runs so agents operate inside policy—not around it.

Value

MCP-compatible HTTP bridge

POST /assistant/mcp implements tools/list and tools/call over JSON-RPC. Hosts like Cursor call evercore_list_routes and evercore_call_endpoint with the caller's Bearer key.

Scopes bound to every action

API keys carry granular scopes (files:write, profiles:read, compliance:write, connectors:read). The bridge proxies only allowlisted routes from the Postman-derived catalog.

Replayable runs and receipts

Console workflows persist steps_log in Postgres; compliance exports and proof receipts return chainId and manifest SHA agents can cite in audits.

How it works

Discover allowlisted tools

tools/list returns evercore_list_routes (catalog discovery) and evercore_call_endpoint (proxied HTTP). GET /assistant/mcp/tools adds registry metadata for console UIs.

Execute inside API-key scopes

tools/call forwards method, path, query, and JSON body using the caller's Authorization header. Routes outside the allowlist are rejected before upstream fetch.

Attach proof receipts

Uploads, compliance exports, connector events, and trace chains emit chainId, manifests, and verification routes agents can return to operators.

Replay workflow runs

assistant_console_workflow_runs stores steps_log JSON. Dry-run and live runs queue through Encore Pub/Sub; the console agent can resume paused graphs on the next user turn.

Use cases

IDE & MCP hosts

Connect Cursor, Claude Desktop, or custom hosts to POST /assistant/mcp with a scoped API key—same operations as Console, without hand-rolling HTTP clients.

Console copilot

Streaming /assistant/console/chat combines the MCP bridge, ec_* tools, Composio connectors, and workflow runners with Turnstile abuse protection.

Regulated evidence playbooks

Author multi-step graphs in Console, dry-run with steps_log, then promote live runs that call real endpoints with a runner bearer validated per API key.

Security guarantees

Allowlisted routes only

The MCP bridge builds its allowlist from knowledge.generated.ts (Postman tree). Internal helper routes are not callable from chat-safe surfaces.

Scope-enforced Bearer keys

Every proxied call uses the caller's API key. Missing scopes fail at the API gateway—the agent cannot escalate beyond the key you issued.

Durable audit trail

Workflow runs, connector receipts, and compliance manifests persist independently of the model transcript so compliance can replay what happened.

For operators

  • Wire IDE hosts to POST /assistant/mcp or use Encore's official MCP (`encore mcp start`) for live service introspection—keep the two layers separate.
  • Grant least-privilege scopes per agent key; the HTTP bridge rejects routes outside the embedded allowlist.
  • Use GET /assistant/console/workflows/:id/runs to inspect dry-run and live execution logs before promoting playbooks.

For buyers

  • Agents inherit the same profiles, retention, connector policy, and evidence exports as human operators.
  • Auditors get replayable step logs and canonical receipts instead of opaque model transcripts.
  • Teams can adopt agentic workflows without a second shadow API or unaudited integration path.

Is this the same as Encore's IDE MCP server?

No. encore mcp start exposes app metadata to editors (services, traces, databases). POST /assistant/mcp is Evercore's authenticated HTTP bridge for product API actions with your Bearer key.

Does the marketing docs assistant use MCP?

/assistant/docs/chat is stateless RAG over the API catalog. Console copilot (/assistant/console/chat) uses the MCP executor, workflows, and optional Composio tools with persisted sessions.

Can agents call SmartWeave through MCP?

Only if the route appears in the allowlisted catalog and the API key has the required scopes. SmartWeave remains a separate protocol extension—see /platform/smartweave for contract APIs.