Read Barion wallet balances, transaction history and item details in Barion. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Barion connector, then ask in plain words. The AI picks the tools.
For business owners and finance staff who check a Barion business wallet.
List the currency accounts of the wallet with their balances. Use the balances for a quick cash position check.
List the wallet transaction history, newest first, up to 20 items per call. Pass the Id of the last item to read older items.
Find the item in the history list, then read its full details. Details cover payments, fees, transfers, withdrawals, refunds and top-ups.
The login page asks for your Barion wallet API key.
Create or copy it on secure.barion.com under Wallet → Access. Wallet keys work for business accounts only, and a shop POS key will not work here. The key is used only to call the Barion API on your behalf; it is never shown to anyone.
Open Customize → Connectors → + Add → Add custom connector, then enter the name Barion and this URL:
The Claude Free plan allows one custom connector.
Team and Enterprise: an Owner adds it for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"barion": {
"url": "https://barion.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"barion": {
"type": "http",
"url": "https://barion.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Barion wallet API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+per user | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Barion server only. Ask your AI to run barion_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with barion_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with barion_upgrade before then undoes the cancel. Or write to [email protected].
barion_list_accountsbarion_list_historybarion_get_history_itembarion_usage_statusbarion_request_featurebarion_upgradebarion_cancel_subscriptionCheck the balance of each wallet account. Review recent wallet transactions. Look up the details of one wallet item. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Barion. The server calls the Barion API with your own Barion access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Barion wallet API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Barion wallet API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Barion API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Barion.
All 3 Barion tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Barion server only. Cancel any time: your paid plan then runs to the end of the paid period. Run barion_usage_status to see how many calls you used.
Ask the AI to run barion_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run barion_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with barion_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.