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.matera.com 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.
MATERA_CLIENT_ID, MATERA_CLIENT_SECRET, MATERA_BASE_URLValues 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": {
"matera": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-matera"
],
"env": {
"MATERA_CLIENT_ID": "your-value",
"MATERA_CLIENT_SECRET": "your-value",
"MATERA_BASE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add matera --env MATERA_CLIENT_ID=your-value --env MATERA_CLIENT_SECRET=your-value --env MATERA_BASE_URL=your-value -- npx -y @codespar/mcp-materaFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"matera": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-matera"
],
"env": {
"MATERA_CLIENT_ID": "your-value",
"MATERA_CLIENT_SECRET": "your-value",
"MATERA_BASE_URL": "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": {
"matera": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codespar/mcp-matera"
],
"env": {
"MATERA_CLIENT_ID": "your-value",
"MATERA_CLIENT_SECRET": "your-value",
"MATERA_BASE_URL": "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.
MATERA_BASE_URL 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 7, 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: MATERA_CLIENT_ID, MATERA_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, FlyDocs
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.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
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.matera.com, the host this server calls, does 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 withMATERA_BASE_URL. To bring the package back, open an issue in mcp-dev-latam with the provider's documented base URL.
MCP server for Matera — Brazilian core-banking infrastructure (BaaS) for fintechs building on top of Pix, DICT, and Pix Automático
Matera is core-banking infrastructure, not a PSP. Per vendor case studies it processes roughly 10% of Brazil's Pix transactions. Its customer is a fintech building on top of Pix — issuing accounts, moving money through DICT, registering Pix Automático agreements — not a merchant accepting Pix (that's what Zoop / Asaas / Mercado Pago are for).
This opens a segment in the CodeSpar catalog distinct from PSP servers: fintech-building-on-top-of-Pix. Matera sits under banking alongside Stark Bank and Open Finance, not under payments.
Use Matera when an agent needs to:
Add to ~/.config/claude/claude_desktop_config.json:
{
"mcpServers": { "matera": { "command": "npx", "args": ["-y", "@codespar/mcp-matera"], "env": { "MATERA_CLIENT_ID": "your-client-id", "MATERA_CLIENT_SECRET": "your-client-secret" } } } }
claude mcp add matera -- npx @codespar/mcp-matera
Add to .cursor/mcp.json or .vscode/mcp.json:
{
"servers": { "matera": { "command": "npx", "args": ["-y", "@codespar/mcp-matera"], "env": { "MATERA_CLIENT_ID": "your-client-id", "MATERA_CLIENT_SECRET": "your-client-secret" } } } }
| Tool | Purpose |
|---|---|
create_pix_charge_static | Create a static Pix charge (reusable QR code tied to a merchant Pix key). |
create_pix_charge_dynamic | Create a dynamic Pix charge (single-use QR with expiration). |
get_pix_charge | Retrieve a Pix charge (static or dynamic) by txid. |
list_pix_charges | List immediate Pix charges (BCB /cob) with date and status filters. |
update_pix_charge | Update an immediate Pix charge (BCB PATCH /cob/{txid}). |
create_pix_charge_due | Create a due-dated Pix charge (BCB /cobv — Pix com Vencimento). |
get_pix_charge_due | Retrieve a due-dated Pix charge (BCB GET /cobv/{txid}). |
create_pix_payment | Initiate an outbound Pix transfer (ordem de pagamento). |
get_pix_payment | Retrieve an outbound Pix payment by endToEndId. |
refund_pix_payment | Refund (devolução) a Pix payment. |
list_pix_payments | List outbound Pix payments with optional filters. |
list_pix_received | List inbound Pix (Pix recebidos) credited to merchant accounts in a date range. |
resolve_pix_key | Resolve a Pix DICT key to the account holder's identity and ISPB/branch/account. |
list_dict_keys | List DICT keys registered to the merchant's accounts on Matera. |
register_dict_key | Register (claim) a DICT key for a merchant account on Matera. |
delete_dict_key | Delete a DICT key the merchant owns. |
create_pix_automatico | Register a Pix Automático recurrence (BCB 2025 recurring Pix product, /rec). |
get_pix_automatico | Retrieve a Pix Automático recurrence by idRec. |
cancel_pix_automatico | Cancel an active Pix Automático recurrence. |
get_account_balance | Get the current balance of a Matera-managed account. |
get_account_statement | Get the statement (extrato) of a Matera-managed account in a date range. |
internal_transfer | Book a transfer between two accounts both held on Matera (TED-interno / transferência interna). |
Matera's public doc index states that server integration uses `secret-key` + `data-signature` headers, while OAuth2 is scoped to mobile / web-UI integrations (doc-api.matera.com). The v0.1-alpha scaffold currently implements the OAuth2 client-credentials path against POST /auth/token. That pairing is almost certainly wrong for server-to-server use and will be replaced with the signed-request scheme once we can validate against a live sandbox — see the "Status" section below.
| Variable | Required | Description |
|---|---|---|
MATERA_CLIENT_ID | Yes | OAuth2 client_id issued by Matera |
MATERA_CLIENT_SECRET | Yes | OAuth2 client_secret (secret) |
MATERA_BASE_URL | No | API base URL. Defaults to https://api.matera.com. Sandbox URL varies per product line — ask your Matera contact. |
v0.1.0-alpha.1 — tool surface is stable, wire paths are NOT yet verified.
On 2026-04-24 we attempted to validate every endpoint path against doc-api.matera.com. The doc site is reachable in a browser but could not be fetched from our automation environment (DNS / network-gated; no login wall observed). Public search snippets and third-party references confirm the product surface (Pix charges, Pix payments, DICT, Pix Automático) and the authentication model (server = secret-key + data-signature; OAuth2 = end-user only) but do not surface the exact URL paths.
Until we can run the server against a live Matera sandbox, the following remain assumed, not verified:
| Area | Value in code | Why it's suspect |
|---|---|---|
| Token endpoint | POST /auth/token (Basic auth, grant_type=client_credentials) | Likely wrong for server integration — see Authentication |
| Pix charges | /pix/charges/static, /pix/charges/dynamic, /pix/charges/{txid} | Matera likely follows BCB's /cob (immediate) / /cobv (dated) naming |
| Pix payments | /pix/payments, /pix/payments/{e2eid}, /pix/payments/{e2eid}/refund | BCB spec names refunds /pix/{e2eid}/devolucao/{id} |
| DICT lookup | GET /pix/dict/{key}, GET /pix/dict/keys | BCB DICT is RSFN-gated; Matera exposes its own wrapper. Exact path unknown. |
| Pix Automático | POST /pix/automatico | Almost certainly a placeholder. BCB 2025 spec uses POST /rec (recurrence) + /cobr/{txid} (recurring charge). |
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 Matera tenant today will produce 404s on most calls.
Track the verification work in the repo issues; PR welcome from anyone with a Matera sandbox.
secret-key + data-signature) for endpoints that require itWant to contribute? Open a PR or request a tool.
Need governance, budget limits, and audit trails for agent-initiated bank transfers? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
MIT