Mcp Persona

io.github.codesparPublished by GitHub account codesparv0.2.2Updated Oct 24, 2026

MCP server for Persona — developer-first identity verification + KYC (inquiries, accounts, reports)

VerifiedSTDIODesktop onlySecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Local MCP server for Persona identity verification and KYC, letting an assistant create and manage inquiries, accounts, reports and cases.

What you can do
  • Create, retrieve, list, approve, decline, redact and resume verification inquiries
  • Create, update, list and retrieve persistent end-user accounts
  • Run standalone reports and list or retrieve report details
  • Open, list and retrieve investigation cases and add case tags
  • List inquiry templates and webhook subscriptions
When to use it
Useful when you build identity verification or KYC flows on Persona and want an assistant to drive inquiries, accounts, reports and review cases from the editor or chat instead of the dashboard.
Requirements
Runs locally via npx from the npm package, with Node.js. Requires a Persona API key in PERSONA_API_KEY, sent as a bearer token; PERSONA_API_VERSION optionally pins the API version. Network access to Persona's API is needed.
Before you install
The API key grants access to identity verification data, so keep it out of shared configs. Tools read and return personal data such as names, birthdates, addresses and report details, and can approve, decline, redact or update records, which changes real verification outcomes. Redaction is destructive and tied to erasure requests.

Installation

In SourceWeft

  1. Open Mcp Persona in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@codespar/mcp-persona

MCP server for Persona — modern developer-first identity verification and KYC.

Persona is the programmable identity layer favoured by modern startups and fintechs that prioritise DX and template-driven workflows. Instead of a fixed KYC pipeline, you compose inquiry templates in the Persona dashboard that reuse building blocks — document, selfie, database, phone, bank — and Persona orchestrates the hosted flow.

Fourth entry in CodeSpar's identity category. Where it fits alongside the others:

ProviderPositioning
UnicoBR leader — local PEP, court records, Receita Federal biometric pool
OnfidoGlobal challenger — document + facial similarity across 195+ countries
JumioGlobal enterprise — deeper fraud intelligence, longer operator track record
PersonaModern developer-first — great DX, template-driven programmable workflows

Pick Persona when you want to ship fast, iterate on the flow without a vendor ticket, and wire verification into your own product surfaces.

Tools (20)

ToolPurpose
create_inquiryCreate a Persona inquiry — a verification session bound to an inquiry template you configured in the Person...
retrieve_inquiryRetrieve an inquiry by id.
list_inquiriesList inquiries, filterable by reference-id (your internal user id) or status.
approve_inquiryMark an inquiry as approved.
decline_inquiryMark an inquiry as declined.
redact_inquiryRedact an inquiry (GDPR right-to-erasure).
create_accountCreate a persistent Persona account — a long-lived end-user record that multiple inquiries can attach to.
retrieve_accountRetrieve a Persona account by id, including summary PII and linked inquiries / verifications.
list_reportsList reports — individual verification artifacts (e.g.
retrieve_reportRetrieve a single report by id — returns the full verification detail (matches, scores, raw source data).
create_caseOpen a case — a workspace for an ongoing investigation tied to one or more inquiries / accounts.
resume_inquiryResume a paused inquiry — returns a fresh one-time session token / link so the end user can continue a flow...
update_accountPatch attributes on an existing Persona account (e.g.
list_accountsList Persona accounts, filterable by reference-id (your internal user id) or email.
run_reportCreate and run a standalone Persona report — not tied to an inquiry flow.
retrieve_caseRetrieve a case by id — full detail including status, assignee, linked objects, attached fields, and tags.
list_casesList investigation cases, filterable by status, assignee, or priority.
add_case_tagAdd a tag to a case.
list_templatesList inquiry templates configured in your Persona dashboard — returns each template's id (itmpl_...), name,...
list_webhooksList configured webhook subscriptions (Persona calls them 'Webhook subscriptions').

Flow

create_inquiry (inquiry-template-id=itmpl_...)    -> user completes Persona-hosted flow (doc + selfie + whatever the template runs)    -> retrieve_inquiry   (poll until status = 'completed' | 'approved' | 'declined' | 'needs_review')    -> approve_inquiry / decline_inquiry   (record your final decision)    -> list_reports / retrieve_report       (for standalone reports like watchlist / adverse-media)

Accounts (create_account / retrieve_account) persist end-user records across inquiries — attach future sessions via account-id on create_inquiry.

Cases (create_case) open a workspace for ongoing investigations (periodic re-verification, flagged users, manual review).

Install

bash
npm install @codespar/mcp-persona

Environment

bash
PERSONA_API_KEY="..."              # API key (required, secret)PERSONA_API_VERSION="2023-01-05"   # Optional. Sent as Persona-Version header.

Authentication

Authorization: Bearer <PERSONA_API_KEY>Persona-Version: 2023-01-05

The server handles both headers automatically.

JSON:API envelope

Persona uses a JSON:API-style request envelope: every POST body is wrapped as { data: { attributes: {...} } }. This server handles the wrapping for you — tool inputs mirror the inner attributes shape directly, with kebab-case keys per Persona's convention:

json
{  "inquiry-template-id": "itmpl_ABC123",  "reference-id": "user_42",  "fields": {    "name-first": "Ada",    "name-last": "Lovelace",    "birthdate": "1815-12-10",    "address-country-code": "US"  }}

The server sends it on the wire as:

json
{ "data": { "attributes": { "inquiry-template-id": "itmpl_ABC123", ... } } }

Run

bash
# stdio (default — for Claude Desktop, Cursor, etc)npx @codespar/mcp-persona
# HTTP (for server-to-server testing)MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-persona

When to pick Persona vs other identity providers

SignalPick
Fast-moving startup / fintech, DX matters, want to iterate on flowPersona
Need custom workflow reusing doc + selfie + bank + phone verificationsPersona
User is Brazilian, need CPF + Receita Federal biometric matchUnico
Global coverage across 195+ countries, regulated fintech AML/PEPOnfido
Bank / large regulated marketplace needing deep fraud intelligenceJumio

Enterprise

Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Source: packages/identity/persona/README.md at commit d0a519a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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