Bankstatemently MCP server
Commit Oct 10, 2026Converts PDF bank statements into structured transactions, accounts, and balances.
Also known as bankstatemently/plugins, plugins
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 2.1.0
- Last commit
- Oct 10, 2026
- License
- MIT
What is Bankstatemently MCP?
Bankstatemently converts PDF bank statements into structured transactions, accounts, and balances.
Summary generated from the project's README
About Bankstatemently MCP server
Bankstatemently provides a way to transform PDF bank statements into organized data including transactions, accounts, and balances. This server is designed for developers and automated systems that need to process financial documents into structured formats. It supports various connection methods including a hosted HTTP transport, a local stdio implementation, and integration through the Claude Code marketplace.
Users can set up the server using browser-based OAuth for interactive sessions or provide an API key for headless environments like CI/CD pipelines. When using the hosted version, the server requires an X-API-Key header rather than a standard Bearer token. For local execution via stdio, you can clone the repository and run the node process directly. The toolset allows for converting files, listing statements, checking credits, and performing benchmark evaluations.
What you can do with it
- 1Convert PDF statementsTransform a PDF bank statement into a structured list of transactions and balances.
- 2Automate financial data extractionUse an API key in a headless CI environment to process documents without manual login.
- 3Evaluate conversion accuracyRun benchmark evaluations to test the quality of the statement conversion process.
Written from the project's README. Every use case is checked against a quote from it.
How to install Bankstatemently MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Bankstatemently MCP in Claude Code
$ claude mcp add --transport http plugins https://api.bankstatemently.com/mcpInstall Bankstatemently MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"plugins": {
"url": "https://api.bankstatemently.com/mcp"
}
}
}Install Bankstatemently MCP in VS Code
.vscode/mcp.json
{
"servers": {
"plugins": {
"type": "http",
"url": "https://api.bankstatemently.com/mcp"
}
}
}Install Bankstatemently MCP in VS Code CLI
$ code --add-mcp '{"name":"plugins","type":"http","url":"https://api.bankstatemently.com/mcp"}'Install Bankstatemently MCP in Codex
$ codex mcp add plugins --url https://api.bankstatemently.com/mcpInstall Bankstatemently MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.plugins] url = "https://api.bankstatemently.com/mcp"
Install Bankstatemently MCP in Gemini CLI
$ gemini mcp add -s user --transport http plugins https://api.bankstatemently.com/mcpInstall Bankstatemently MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"plugins": {
"url": "https://api.bankstatemently.com/mcp",
"type": "http"
}
}
}Configuration
BANKSTATEMENTLY_API_KEY
| Name | Description | |
|---|---|---|
| BANKSTATEMENTLY_API_KEY | — |
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablebankstatemently/plugins is public and reachablegithub.com/bankstatemently/plugins ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-10github.com/bankstatemently/plugins ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 640 msPass
README
View on GitHubbankstatemently/plugins
Marketplace plugins for Bankstatemently — convert bank statements.
Install via Claude Code marketplace
/plugin marketplace add bankstatemently/plugins
/plugin install bankstatemently@bankstatemently
After installing, enable the plugin. The first tool call opens your browser to sign in; the plugin asks for no settings.
For a headless setup (CI, scripts), skip the plugin and add the server directly with an API key — see below. Get a key at bankstatemently.com/developer.
Plugins
- bankstatemently — MCP server for converting bank statements. Convert PDFs, list statements, check credits, run benchmark evaluations.
Claude Code direct install (no plugin)
Add the hosted MCP server directly and sign in with your browser:
claude mcp add --transport http bankstatemently https://api.bankstatemently.com/mcp
For a headless setup, pass an API key in the X-API-Key header instead (the server rejects Authorization: Bearer):
claude mcp add --transport http bankstatemently https://api.bankstatemently.com/mcp \
--header "X-API-Key: <your-bsk_live_key>"
Codex
Codex has native OAuth support. This one command detects our server's discovery metadata and opens your browser to sign in — no key is ever stored:
codex mcp add bankstatemently --url https://api.bankstatemently.com/mcp
For headless or CI setups where a browser sign-in isn't possible, use an API key via the mcp-remote bridge instead. Export the key in the shell that launches Codex, before it starts:
export BANKSTATEMENTLY_API_KEY=bsk_live_...
codex mcp add bankstatemently -- npx -y mcp-remote@latest https://api.bankstatemently.com/mcp --header "X-API-Key: ${BANKSTATEMENTLY_API_KEY}"
Codex doesn't yet surface plugin-declared MCP servers into sessions, so the plugin install above (and its bundled skill) isn't available in Codex today — use the commands above instead.
Credential managers & sandboxed clients: never fetch a secret from Keychain, 1Password, or another credential manager inside the MCP server command itself — Codex runs that command sandboxed at tool discovery, so a credential-manager lookup dies silently and the server's tools never appear. Export the key in the shell that launches Codex instead. Also note that mcp-remote logs its resolved header values to stderr, so a wrapper-resolved key can end up in your client logs.
Run over stdio
For stdio-only clients (Claude Desktop's config file, Cursor, headless
setups) or a directory scanner that launches the server locally, clone the
public repo and run the self-contained mcp-stdio server directly — no
Docker, no bridge process:
git clone https://github.com/bankstatemently/plugins.git
cd plugins/mcp-stdio
npm install --omit=dev
BANKSTATEMENTLY_API_KEY=bsk_live_... node dist/stdio.js
BANKSTATEMENTLY_API_KEY is optional at startup: initialize/tools/list
answer with no network call and no key either way, so an uncredentialed
directory probe still sees the full tool list. A tools/call with no key
returns the same auth-required result the hosted server returns. Export the
key in the shell or runtime environment that launches the process — never
resolve it inside the MCP command (a credential-manager lookup inside a
sandboxed client's command dies silently, same caveat as the Codex section
above).
Bankstatemently MCP questions
How do I add Bankstatemently MCP to Claude Code?
Run claude mcp add --transport http plugins https://api.bankstatemently.com/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Bankstatemently MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I install Bankstatemently via Claude Code?
You can install it using the command /plugin marketplace add bankstatemently/plugins followed by /plugin install bankstatemently@bankstatemently.
How can I use Bankstatemently in a headless or CI setup?
For headless setups, you can add the server directly using an API key in the X-API-Key header.
Does the server require an API key to list tools?
No, the API key is optional at startup for certain operations; initialize and tools/list will work without a network call or key.