- Home
- MCP servers
- Monobank
Monobank
- typescript
1
GitHub Stars
typescript
Language
5 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"aler1x-monobank-mcp": {
"command": "npx",
"args": [
"-y",
"@alerix/monobank-mcp"
],
"env": {
"MONOBANK_API_TOKEN": "your_token_here"
}
}
}
}You can expose your Monobank data as MCP tools using a Node.js and TypeScript server. This setup lets you fetch client info and account statements through standard MCP tools, enabling seamless integration with your MCP client workflows while keeping your tokens and credentials secure.
How to use
Start your MCP client and connect to the Monobank MCP server to access two built-in tools: get_client_info and get_statement. get_client_info returns client details, accounts, and jars metadata, while get_statement retrieves account transactions for a defined period (up to 31 days). Use these tools to integrate personal banking data into your MCP-enabled automation and dashboards.
How to install
Prerequisites you need before installation: Node.js and npm (or yarn). You will run a published MCP server package through your MCP configuration.
{
"mcpServers": {
"monobank-mcp": {
"command": "npx",
"args": ["-y", "@alerix/monobank-mcp"],
"env": {
"MONOBANK_API_TOKEN": "your_token_here"
}
}
}
}
Starting and running
In your environment, set the token and start the server using your MCP client configuration. The server will expose two tools immediately after launch.
export MONOBANK_API_TOKEN=your_token_here
npm start
Or with a direct environment variable in one line
MONOBANK_API_TOKEN=your_token_here npm start
## Notes on configuration and tokens
Your personal Monobank API token is required to access data. Configure it in the environment or within your MCP config as MONOBANK\_API\_TOKEN. Ensure your token permissions align with the two available tools.
## Security and best practices
Keep your API token secure: do not commit it to version control. Use environment variable management or secret stores in your deployment environment. Rotate tokens periodically and restrict the scope to MCP access only.
## Available tools
### get\_client\_info
Fetches client profile, accounts and jars metadata.
### get\_statement
Retrieves account transactions for a specified account and time window (up to 31 days).