The Revio Insight MCP server is live — connect Claude, ChatGPT, or Copilot in minutes. Get started →
AI AgentSignals Meeting PreparationAudience Builder MCP Server About usSecurityContact Book a demo
MCP Server · Live

Your bank's AI agent,
everywhere you work

The Revio Insight MCP server connects Claude, ChatGPT, Microsoft Copilot, and any MCP client to your bank's intelligence — opportunities, customers, competitors, and audiences. Read-only by design, signed in with OAuth.

Works with
ClaudeChatGPTCopilot+ all MCP clients

Works with every major MCP client

Claude
ChatGPT
Microsoft Copilot
Cursor & Claude Code
Any MCP Client
Capabilities

One agent. Zero integration work.

Everything the Revio Insight Agent can do, exposed to your AI tools through the Model Context Protocol.

Ask the way you already talk

Capabilities are named by intent — find opportunities, look up a customer, prepare for a meeting — so your AI host routes each question to the right one automatically. No commands to learn.

The full agent behind every question

Every question runs the complete Revio Insight Agent loop — opportunities across every category Revio detects, customers, competitors, branches, relationship managers, and audiences.

Audiences: the one write

Build, preview, and save audiences from your AI tool. Saved lists land in Revio's Custom Audiences, attributed to the signed-in user — ready to explore and export.

Read-only by design

The MCP surface cannot create tasks, modify records, or delete anything — enforced in the agent's instructions and again at execution time.

OAuth 2.1 sign-in

Per-user login with MFA and an explicit consent screen — tokens are short-lived, bank-bound, and revocable. API keys with IP allowlists cover automation.

Budgets and receipts

A monthly AI budget per institution, enforced before each request — and a log of every call: the question, tokens, cost, latency, and who asked.

Real conversations

Ask from wherever you already are

The same questions your team asks in Revio — answered inside Claude, ChatGPT, and Copilot.

Setup

Connected in minutes

No infrastructure to run, no custom integration. Enable MCP for your institution, then each user signs in from their own AI tool.

1

Enable MCP in Revio

Settings → Integrations → MCP. An admin with MCP permission turns it on and sets the monthly AI budget for your institution.

2

Connect your AI tool

Add the connector in Claude or ChatGPT and sign in with your Revio account — MFA and a consent screen included. For automation, create an API key with an optional IP allowlist instead.

3

Start asking

Revio's capabilities appear in your AI tool automatically. Ask about opportunities, customers, and competitors — the right one is picked by intent.

# claude.ai (or Claude Desktop)
# Settings → Connectors → Add custom connector

Name: Revio Insight
URL:  <your Revio MCP URL>
# Copy it from Revio → Settings → Integrations → MCP

# Sign in with your Revio account (MFA),
# approve the consent screen — done.
✓ Revio Insight connected
# ChatGPT → Settings → Connectors → Add

Name: Revio Insight
MCP server URL:
  <your Revio MCP URL>
Authentication: OAuth

# Sign in with your Revio account when
# prompted. Requires a ChatGPT plan with
# connectors enabled.
# For automation & CLI clients:
# Revio → Settings → Integrations → MCP
# → Create API key (optional IP allowlist)

claude mcp add --transport http \
  revio <your-revio-mcp-url> \
  --header "Authorization: Bearer <your-key>"

claude mcp list
✓ revio  connected
Intent routing

One agent, many doors

Capabilities are named the way people ask. Your AI host reads the intent — "prep me for my call with…" — and routes it to the right one without anyone saying "Revio."

Every entry point runs the same full agent loop — one permission model, one behavior

Each call is stateless on Revio's side — your AI tool carries the thread and passes context forward

Every answer states the data window used — "data through July 31" comes standard

Internal identifiers stay internal — the agent is instructed never to expose them

Claude
routing by intent — no tool names needed
U
Prep me for my 2pm with Harbor Café Group
R
Harbor Café Group — 4-year relationship, $310K in deposits, settling $1.2M/yr through an outside processor. Talking points: 1) merchant services with their observed volume, 2) idle balance → money market, 3) the operating line renews in March.
U
Who else settles with outside processors?
R
118 accounts — $12.3M in Merchant Services opportunities, trailing 365 days. Top three: Ridgeline Builders, Harbor Café Group, Cedar Auto Service.
The one write

Ask anywhere.
Save to Revio.

The MCP surface is read-only with a single, deliberate exception: saving an audience. Build the list in Claude or ChatGPT, confirm, and it's waiting in Revio for the campaign.

Preview first — customer count and balances before anything persists
Saves only after you explicitly confirm
Attributed to the signed-in user — auditable like everything else
Opens in the Audience Builder for filters, exports, and HubSpot sync
Explore Audience Builder
Custom Audiences — saved from MCP
Saved this week
Square Settlements — Displacement118 customers
CD Renewal Q483 customers
1st Security — Conquest64 customers
Each audience re-runs its criteria live — open it, refine it, export it, or sync it to HubSpot on a schedule.
Security

Enterprise-grade from day one

Per-user identity, per-institution isolation, and a receipt for every request.

OAuth 2.1 + PKCE

Per-user sign-in with MFA, an explicit consent screen, and bank-bound tokens. Refresh and revocation built in — no shared secrets floating around.

API keys for automation

Bearer keys created in Revio, with optional CIDR IP allowlists — ["52.10.0.0/16"] — and expiry. Revoke any key instantly.

Read-only by design

No task creation, no edits, no deletes — blocked in the agent's instructions and again at execution. The single exception: an audience you confirmed saving.

Budgets & audit trail

A monthly USD cap on AI spend per institution, checked before and during every request — and a per-call log with tokens, cost, latency, and principal.

Frequently asked questions

MCP (Model Context Protocol) is an open standard that lets AI tools — Claude, ChatGPT, Copilot — discover and call external tools securely. Revio implements it once, and every MCP-compatible assistant your team adopts can use your bank's intelligence. No per-platform integration projects, ever.
Claude (claude.ai and Claude Desktop) and ChatGPT have guided setup in Revio. Anything that speaks MCP over Streamable HTTP works too — Microsoft Copilot, Claude Code, Cursor, and custom agents via API key.
It never touches your core — Revio is fed by one-way file feeds. Within Revio, the MCP surface is read-only with one exception: saving an audience after you explicitly confirm. It cannot create tasks, modify records, or delete anything.
Two ways. Humans sign in with OAuth 2.1: their own Revio credentials, MFA, and a consent screen — tokens are short-lived and revocable. Automation uses API keys created in Revio, optionally restricted to CIDR IP ranges. Both require MCP to be enabled for your institution.
Each MCP call is stateless on Revio's side — by design. Your AI tool owns the conversation and passes context forward, which keeps the server surface simple to audit. Inside Revio's own chat, conversations are fully persistent, searchable, and shareable.
MCP calls use AI capacity (AWS Bedrock) metered against a monthly budget set per institution. Requests are declined once the cap is reached — no surprise bills — and every call is logged with its token count and cost.
Complex multi-tool questions can take a couple of minutes. The server supports up to 300 seconds per call — set your client timeout accordingly, e.g. MCP_TOOL_TIMEOUT=300000 in Claude Code or "timeout": 300000 in .mcp.json.

Bring your bank's data
to your AI tools

Already on Revio? Enable MCP in Settings → Integrations and connect in minutes. Not yet? Start with the demo.

Book a demo

See your book from inside Claude

Thirty minutes. We'll connect a live MCP client, route real questions through it live, and walk your security team through OAuth, budgets, and the audit log.

Live connection to Claude or ChatGPT — watch intent routing work

The full security story: OAuth 2.1, MFA, IP allowlists, read-only guarantees

Budget controls and per-request logging for your compliance team

We reply within one business day. No newsletters, no drip campaigns.

Request received

We'll email you within one business day to set up a time. It's a 30-minute call — bring your questions.