Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
DEPRECATED: no live endpoint (api.dock.tech does not resolve)
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
DOCK_CLIENT_ID, DOCK_CLIENT_SECRET, DOCK_ENV标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"dock": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-dock"
],
"env": {
"DOCK_CLIENT_ID": "your-value",
"DOCK_CLIENT_SECRET": "your-value",
"DOCK_ENV": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add dock --env DOCK_CLIENT_ID=your-value --env DOCK_CLIENT_SECRET=your-value --env DOCK_ENV=your-value -- npx -y @codespar/mcp-dock运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"dock": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-dock"
],
"env": {
"DOCK_CLIENT_ID": "your-value",
"DOCK_CLIENT_SECRET": "your-value",
"DOCK_ENV": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"dock": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codespar/mcp-dock"
],
"env": {
"DOCK_CLIENT_ID": "your-value",
"DOCK_CLIENT_SECRET": "your-value",
"DOCK_ENV": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
DOCK_ENV env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 codespar 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:DOCK_CLIENT_ID, DOCK_CLIENT_SECRET
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.2.0-alpha.4)于40天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, topo^alpin
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Deprecated: no live endpoint. Measured on 2026-09-27 against two public DNS resolvers (8.8.8.8 and 1.1.1.1):
api.dock.tech(production) andsandbox.api.dock.tech(sandbox) do not resolve in DNS. No tool in this server reaches a service. The package is deprecated on npm and stays in this repository for reference only. If you have a working endpoint, point the server at it withDOCK_BASE_URL. To bring the package back, open an issue in mcp-dev-latam with the provider's documented base URL.
MCP server for Dock — Brazilian Banking-as-a-Service (accounts, Pix, card issuing) for fintechs and embedded-finance products
Dock is one of the two dominant BaaS providers in Brazil. Together with Matera, they power most BR fintechs.
Matera vs Dock — pick one, same commerce patterns:
| Matera | Dock | |
|---|---|---|
| Core strength | Pix-focused core banking | Broader BaaS: accounts + Pix + card issuing |
| Historical root | Core-banking platform | Card-issuing platform that expanded into accounts + Pix |
| Typical customer | Fintech building on top of Pix | Fintech / retailer issuing branded cards + accounts |
| Pix Automático | Live (2025 BCB product) | Roadmap |
BR fintechs usually pick one based on contract terms and pricing. Agents building fintech products can target both — the commerce patterns are identical; only the vendor relationship changes. This server exposes Dock's surface in the same shape as @codespar/mcp-matera so an agent can swap backends without rewriting tool-call logic.
Use Dock when an agent needs to:
Add to ~/.config/claude/claude_desktop_config.json:
{
"mcpServers": { "dock": { "command": "npx", "args": ["-y", "@codespar/mcp-dock"], "env": { "DOCK_CLIENT_ID": "your-client-id", "DOCK_CLIENT_SECRET": "your-client-secret", "DOCK_ENV": "sandbox" } } } }
claude mcp add dock -- npx @codespar/mcp-dock
Add to .cursor/mcp.json or .vscode/mcp.json:
{
"servers": { "dock": { "command": "npx", "args": ["-y", "@codespar/mcp-dock"], "env": { "DOCK_CLIENT_ID": "your-client-id", "DOCK_CLIENT_SECRET": "your-client-secret", "DOCK_ENV": "sandbox" } } } }
| Tool | Purpose |
|---|---|
create_account | Create a digital account for an end user (CPF holder) on Dock. |
get_account | Retrieve a Dock account by id. |
send_pix | Initiate an outbound Pix transfer from a Dock account to any Pix key in BR. |
get_pix | Retrieve an outbound Pix payment by endToEndId. |
create_pix_qr_static | Create a static Pix QR (reusable, tied to a merchant Pix key). |
create_pix_qr_dynamic | Create a dynamic Pix QR (single-use, expiring). |
refund_pix | Refund (devolução) a Pix payment. |
resolve_dict_key | Resolve a Pix DICT key to the account holder's identity and ISPB/branch/account. |
issue_card | Issue a card (debit / credit / prepaid / virtual) against a Dock account. |
get_card | Retrieve a card by id. |
list_accounts | List Dock accounts under the merchant. |
freeze_account | Freeze (block) a Dock account. |
unfreeze_account | Unfreeze a previously frozen Dock account, restoring Pix and card operations. |
block_card | Block a card temporarily (reversible). |
unblock_card | Unblock a card that was previously blocked (reversible). |
change_card_status | Change a card's lifecycle status: ACTIVE / BLOCKED / CANCELED. |
list_transactions | List transactions on a Dock account (Pix in/out, card auths, fees, transfers). |
get_transaction | Retrieve a single transaction by id. |
create_webhook | Register a webhook endpoint to receive Dock event notifications (account.*, pix.*, card.*, transaction.*). |
list_webhooks | List all webhook endpoints registered for the merchant. |
OAuth 2.0 Client Credentials. The server calls POST /oauth/token with Basic auth (client_id:client_secret) and caches the bearer token in memory until a minute before expiry.
| Variable | Required | Description |
|---|---|---|
DOCK_CLIENT_ID | Yes | OAuth2 client_id issued by Dock |
DOCK_CLIENT_SECRET | Yes | OAuth2 client_secret (secret) |
DOCK_ENV | No | sandbox (default) or production |
Base URL is derived from DOCK_ENV: https://sandbox.api.dock.tech (sandbox) or https://api.dock.tech (production).
v0.1.0-alpha.1 — tool surface is stable, wire paths are NOT yet verified.
Dock's developer portal at developers.dock.tech redirects to a ReadMe.com login gate. Public docs are not accessible without a Dock merchant contract, so on 2026-04-21 we could not validate the exact URL paths.
The endpoint paths in src/index.ts follow standard BR BaaS conventions (matching Matera's shape and the BCB Pix spec) and are best-guesses. Known-suspect items are flagged inline with TODO(verify) comments:
| Area | Value in code | Why it's suspect |
|---|---|---|
| Token endpoint | POST /oauth/token | Standard candidate, but /oauth2/token or /auth/v1/token also common |
| Pix refund | POST /pix/payments/{e2eid}/refund | BCB spec names refunds /pix/{e2eid}/devolucao/{id} |
| DICT lookup | GET /pix/dict/{key} | BCB DICT is RSFN-gated; Dock's wrapper path unverified |
The 10 tool names and input schemas above are the public contract and will remain stable. Only the internal HTTP calls in src/index.ts will change when we verify against the sandbox. Using this server against a live Dock tenant today may produce 404s on most calls.
PR welcome from anyone with a Dock sandbox.
block_card, unblock_card, set_card_limitsWant to contribute? Open a PR or request a tool.
Need governance, budget limits, and audit trails for agent-initiated bank transfers and card issuance? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
MIT