Persona logoMCP server · Finance and commerce

Persona MCP server

Persona in any MCP client, through Memtro: Persona does not publish this server. Memtro's Persona connector reads Persona through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Persona identity verification: inquiries by status, template, account and date, cases with their status, assignee and SLA, screening reports and whether they matched, accounts and the event log, all without the personal details collected; when you ask, can comment on, assign, re-status and tag cases, approve, decline, expire or send inquiries for manual review, tag inquiries, accounts and reports, and permanently redact an inquiry or account.

Reads

  • persona_list_inquiriesPersona inquiries (one person's run through a verification flow), newest first: status, reference id, template, account…
  • persona_get_inquiryOne Persona inquiry: status, template, account, tags, every lifecycle date, how many verifications ran…
  • persona_list_casesPersona cases (investigations needing a decision), newest first: status, resolution, template, queue, assignee user id, SLA…
  • persona_get_caseOne Persona case: status, resolution, template, queue, assignee user id, dates, SLA, tags and the ids of the inquiries, accounts and reports it holds.
  • persona_list_reportsPersona reports (watchlist, politically exposed person, adverse media, address, phone and similar lookups), newest first: type, status…
  • persona_list_accountsPersona accounts (one per end user, grouping their inquiries and reports), newest first: reference id, account type, status, tags and dates.
  • persona_list_eventsPersona's event log, newest first: event name (inquiry.approved, case.resolved, ...), when it happened and the object it was about.

Acts, when you ask

These change something in Persona. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • persona_add_case_commentAdds a comment to a Persona case, visible to everyone who can open the case in Persona; there is no API to delete it.
  • persona_set_case_statusSets a Persona case's status to one your case template defines (for example a resolved status)…
  • persona_assign_caseAssigns a Persona case to the Persona dashboard user with the email address given; that user becomes its owner and may be notified by Persona.
  • persona_add_tagAdds a tag to a Persona inquiry, case, account or report (the tag is created if it is new); tags can trigger workflows.
  • persona_remove_tagRemoves a tag from a Persona inquiry, case, account or report.
  • persona_approve_inquiryApproves a Persona inquiry, a final identity decision about the person: it stops further progress on the inquiry and triggers your Persona workflows…
  • persona_decline_inquiryDeclines a Persona inquiry, a final identity decision against the person: it stops further progress and triggers your Persona workflows and webhooks…
  • persona_mark_inquiry_for_reviewMarks a Persona inquiry for manual review, which stops further progress on it and triggers your workflows and webhooks.
  • persona_expire_inquiryExpires a Persona inquiry, so the person can no longer continue it with their current session; this triggers your workflows and webhooks.
  • persona_redactPermanently deletes the personal information held for a Persona inquiry (with its verifications and reports) or an account (with all its inquiries…

Connect it

First connect Persona on Dashboard → Connections, then add Memtro to your client once. The Persona tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Persona connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which cases are past their SLA, and who is assigned?
  • › How many inquiries were declined this week?
  • › Which inquiries are waiting for manual review?
  • › Did the screening reports on account ACC-2231 match anything?
  • › Assign case 8812 to Maya Okafor.

Questions

Is this an official Persona MCP server?
No. It is Memtro's MCP server with Memtro's Persona connector behind it: the connector reads Persona through its API with the credentials you connect on Dashboard → Connections, and Persona publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Persona?
Only when you ask, and only what it has been granted: add a comment to a case; set a case's status; assign a case to a Persona user; add a tag to an inquiry, case, account or report; remove a tag from an inquiry, case, account or report; approve an inquiry; decline an inquiry; mark an inquiry for manual review; expire an inquiry; permanently redact an inquiry or account. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Finance and commerce

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time