These tools run the StatementPro.ai MCP server on your own computer from our npm package, @statementpro/mcp, using your API key. Create a key, add one entry to your tool's settings, and ask it to convert a statement.
Before you start
- A StatementPro.ai account with any credit pack. Conversions use purchased credits only.
- An API key. See Create an API key.
- Node.js 22 or later on your computer.
Steps
- In StatementPro.ai, go to Settings › API access and click Create API key. Copy the key now; it's shown only once.
- Add StatementPro.ai to your tool using the setup for it below. Replace
sp_live_...with your key. - Ask your assistant: "How many StatementPro.ai credits do I have left?" If it answers, you're connected.
Claude Code
claude mcp add statementpro --scope user -e STATEMENTPRO_API_KEY=sp_live_... -- npx -y @statementpro/mcp
On Windows (not WSL), use -- cmd /c npx -y @statementpro/mcp at the end instead.
Claude Desktop and Cursor
In Claude Desktop, open Settings › Developer › Edit Config. In Cursor, use ~/.cursor/mcp.json or a project's .cursor/mcp.json. Add:
{
"mcpServers": {
"statementpro": {
"command": "npx",
"args": ["-y", "@statementpro/mcp"],
"env": { "STATEMENTPRO_API_KEY": "sp_live_..." }
}
}
}
If the server doesn't start on Windows, set "command": "cmd" and "args": ["/c", "npx", "-y", "@statementpro/mcp"].
VS Code
Add the server in .vscode/mcp.json. The example in our npm package README asks for your key when the server starts, so the key isn't saved in the file.
Other MCP clients
Any MCP client that can run a local (stdio) server can use the same command, npx -y @statementpro/mcp, with your key in STATEMENTPRO_API_KEY.
Good to know
- Your key stays on your computer and is sent only to StatementPro.ai. Your assistant doesn't see it.
- Your assistant gets a quote before it converts, and results come back as CSV or JSON. The npm package can also save a result to a file.
- It can convert several files one after another.
- It sees conversions made through an assistant or the API, not statements you uploaded on the website.
If something goes wrong
- "STATEMENTPRO_API_KEY is not set": the key isn't in your tool's settings. Add it there.
- "StatementPro rejected the API key": the key is wrong, or it was revoked or regenerated. Copy your current key, or create a new one.
- The server doesn't start: check that
node --versionshows 22 or later. On Windows, try thecmd /csetup above.
The full configuration, Windows notes and troubleshooting are in the npm package README.