Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP server for Persona — developer-first identity verification + KYC (inquiries, accounts, reports)
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
PERSONA_API_KEY, PERSONA_API_VERSION标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"persona": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-persona"
],
"env": {
"PERSONA_API_KEY": "your-value",
"PERSONA_API_VERSION": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add persona --env PERSONA_API_KEY=your-value --env PERSONA_API_VERSION=your-value -- npx -y @codespar/mcp-persona运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"persona": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-persona"
],
"env": {
"PERSONA_API_KEY": "your-value",
"PERSONA_API_VERSION": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"persona": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codespar/mcp-persona"
],
"env": {
"PERSONA_API_KEY": "your-value",
"PERSONA_API_VERSION": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
PERSONA_API_VERSION env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 codespar 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:PERSONA_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.2.2)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Systemdox
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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:
| Provider | Positioning |
|---|---|
| Unico | BR leader — local PEP, court records, Receita Federal biometric pool |
| Onfido | Global challenger — document + facial similarity across 195+ countries |
| Jumio | Global enterprise — deeper fraud intelligence, longer operator track record |
| Persona | Modern 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.
| Tool | Purpose |
|---|---|
create_inquiry | Create a Persona inquiry — a verification session bound to an inquiry template you configured in the Person... |
retrieve_inquiry | Retrieve an inquiry by id. |
list_inquiries | List inquiries, filterable by reference-id (your internal user id) or status. |
approve_inquiry | Mark an inquiry as approved. |
decline_inquiry | Mark an inquiry as declined. |
redact_inquiry | Redact an inquiry (GDPR right-to-erasure). |
create_account | Create a persistent Persona account — a long-lived end-user record that multiple inquiries can attach to. |
retrieve_account | Retrieve a Persona account by id, including summary PII and linked inquiries / verifications. |
list_reports | List reports — individual verification artifacts (e.g. |
retrieve_report | Retrieve a single report by id — returns the full verification detail (matches, scores, raw source data). |
create_case | Open a case — a workspace for an ongoing investigation tied to one or more inquiries / accounts. |
resume_inquiry | Resume a paused inquiry — returns a fresh one-time session token / link so the end user can continue a flow... |
update_account | Patch attributes on an existing Persona account (e.g. |
list_accounts | List Persona accounts, filterable by reference-id (your internal user id) or email. |
run_report | Create and run a standalone Persona report — not tied to an inquiry flow. |
retrieve_case | Retrieve a case by id — full detail including status, assignee, linked objects, attached fields, and tags. |
list_cases | List investigation cases, filterable by status, assignee, or priority. |
add_case_tag | Add a tag to a case. |
list_templates | List inquiry templates configured in your Persona dashboard — returns each template's id (itmpl_...), name,... |
list_webhooks | List configured webhook subscriptions (Persona calls them 'Webhook subscriptions'). |
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).
npm install @codespar/mcp-persona
PERSONA_API_KEY="..." # API key (required, secret)
PERSONA_API_VERSION="2023-01-05" # Optional. Sent as Persona-Version header.
Authorization: Bearer <PERSONA_API_KEY>
Persona-Version: 2023-01-05
The server handles both headers automatically.
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:
{
"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:
{ "data": { "attributes": { "inquiry-template-id": "itmpl_ABC123", ... } } }
# stdio (default — for Claude Desktop, Cursor, etc)
npx @codespar/mcp-persona
MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-persona
| Signal | Pick |
|---|---|
| Fast-moving startup / fintech, DX matters, want to iterate on flow | Persona |
| Need custom workflow reusing doc + selfie + bank + phone verifications | Persona |
| User is Brazilian, need CPF + Receita Federal biometric match | Unico |
| Global coverage across 195+ countries, regulated fintech AML/PEP | Onfido |
| Bank / large regulated marketplace needing deep fraud intelligence | Jumio |
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.
MIT