Stark Bank

@codespar/mcp-stark-bank · v0.2.2

🇧🇷 BrazilBankingAuth · OAuth2live27 tools2 env vars

Banking as a Service: Pix, boleto, TED, statements, and reconciliation. Your agent moves money and tracks every cent.

Get started · free View docs

MIT · runs locally with your own credentials

Limitations

The package manifest does not declare 1 of the 2 variables the code reads.
Hosted calls with a test key are not available: connecting this provider needs credentials it issues to an operator.

DetailsSource on GitHub

Package: @codespar/mcp-stark-bank
Version: 0.2.2
npm dist-tag: latest
Category: Banking
Auth: OAuth2
Country: 🇧🇷 Brazil
License: MIT
Transport: stdio · streamable-http

npm GitHub Server catalog docs

Quickstart

Install, set the credentials, make the first call.

Pick your client. The server runs locally over stdio, with your own credentials.

Add the server to your clientOne config entry. No build step, no SDK required.

Set the environment variables2 variables read by this server's code, listed below.

Restart and make the first callThe agent can call any of the 27 tools. Try create_transfer first.

Hosted MCP Build your own server

terminal

# Claude Code
claude mcp add stark-bank -e STARK_BANK_ACCESS_TOKEN=… -e STARK_BANK_SANDBOX=… -- npx -y @codespar/mcp-stark-bank@0.2.2
# then: /mcp to confirm the server is connected

Environment variables2 variables

STARK_BANK_ACCESS_TOKENAPI key for stark-bankrequiredsecret

STARK_BANK_SANDBOXRead by the code; the package manifest does not declare it.

Names read from the package code (@codespar/mcp-stark-bank@0.2.2). Descriptions and flags come from its manifest. Self-hosted, you hold the credentials.

First call democreate_transfer

"Create a bank transfer"

tools/callcreate_transferresult returned

Tools

What your agent can call.

27 tools, as the package's tools/list returns them.

create_transfer

Create a bank transfer (Pix or TED)

get_transfer

Get transfer details by ID

list_transfers

List transfers with optional filters

create_boleto

Create a boleto payment

get_balance

Get current account balance

create_invoice

Create an invoice (generates Pix QR code)

get_invoice

Get invoice details by ID

list_invoices

List invoices with optional filters

create_pix_request

Create a Pix payment request

get_webhook_events

Get webhook events (payment confirmations, transfers, etc.)

create_payment_request

Create a payment request for approval workflow

get_payment_request

Get payment request details by ID

Names and descriptions come from the package's tools/list (@codespar/mcp-stark-bank@0.2.2). A kind (read, write, delete) is shown only when the package annotates its tools or each tool was verified one by one; neither exists for this server yet.

Compatibility

MCP is a protocol. Any client that speaks it can mount this server.

codespar_discover lists this server's tools, but connecting it needs credentials the provider issues to an operator (a certificate, signed keys or paired headers), which a test key cannot produce.

Protocol

Any MCP client

stdio · streamable-http

Questions

Before you install.

How do I install the Stark Bank MCP server?

Run npx -y @codespar/mcp-stark-bank@0.2.2 and add the config block above to your MCP client: Claude Code, Cursor, Claude Desktop, VS Code, or any MCP-compatible client. No build step, no SDK required.

What can my agent do with Stark Bank?

Stark Bank exposes 27 tools for banking. Your agent calls them directly; the full list is above.

How does Stark Bank authenticate, and how are credentials stored?

Stark Bank uses OAuth2. Self-hosted, you hold the credentials: the server reads them from its environment variables.

How does Stark Bank handle upstream API changes?

Every server is versioned independently on npm. The command on this page pins 0.2.2, the version whose tools are listed here; your agent keeps running it until you change the version.

Is Stark Bank open source? How do I report a bug?

Yes. Stark Bank is MIT-licensed and published on npm as @codespar/mcp-stark-bank, source on GitHub (link in the Details panel). Report issues on the package repository; security issues go to security@codespar.dev, and we respond within 24 hours.

Pairs well with