Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
DEPRECATED: no live endpoint (api.dock.tech does not resolve)
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
DOCK_CLIENT_ID, DOCK_CLIENT_SECRET, DOCK_ENVValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into 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"
}
}
}
}Run this in your terminal
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-dockFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.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"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"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"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
DOCK_ENV envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account codespar, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: DOCK_CLIENT_ID, DOCK_CLIENT_SECRET
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0-alpha.4) reached the registry 40 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, yontu
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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