Steps to follow
- Open AI agents and connect a client supporting MCP Streamable HTTP. With OAuth, approve access in the browser; configure a key only in the client’s protected environment.
- Grant only the permissions needed. Reading, integration setup and test actions have separate scopes; the available tools depend on the granted access.
- For live credentials and creating recurring or bulk invoices, the agent receives an approval URL. Open it, review the exact request, and approve it in the dashboard.
- Verify results using Bankemes state. Revoke an unneeded client in the dashboard; there is no need to put the key in chat or give the agent an OTP.
MCP does not replace the entire dashboard
MCP covers the specific tasks below. Profile and security management, billing consent and some financial-history actions remain in the dashboard. A missing tool is not permission to use a browser session without the owner’s separate authorization.
What the agent does and what the owner approves
| Task | Through MCP | Owner | In the dashboard |
|---|---|---|---|
| Project and integration | Website resource, credentials, webhook, guidance, tests and diagnostics. | Grants project access and separately approves live credentials. | Client authorization and access management. |
| Cashier and Bankemes subscription | Reads state and provides the next setup step or invoice page. | Signs in to Kaspi and pays in the banking app. | OTP, billing phone, consent and disabling future invoices. |
| Customers and recurring invoices | Creates, reads, updates and archives customers; reads schedules and invoices, and creates or manages schedules. | Approves the exact parameters for creating recurring and bulk invoices. | Full history and actions without a dedicated MCP tool. |
| Payments and account state | Tests, payment links, analytics aggregates and authorized diagnostics. | Checks real payments and authorizes application changes. | Profile, password, notifications and manual review of disputed financial operations. |
Your Kaspi password, SMS codes and bank session stay with you. Credentials use protected configuration; access to your project code is granted separately.
For developers and AI agents
The English Markdown reference contains tool schemas, parameters, request examples and access restrictions.
Technical reference in English