Connect Claude, or any client that supports remote MCP servers, to your Billino account. Create invoices, manage clients, record payments and fetch PDFs from a chat or your own tooling.
Pick your client. No installation, just your Billino account.
Open Billino in Claude’s connector directory, choose Connect and sign in with your Billino account. No key needed.
You need an API key. Create one under Settings → API. It is free on every plan.
Run this, then use /mcp inside Claude Code to check the connection.
claude mcp add --transport http billino https://api.billino.io/mcp \ --header "Authorization: Bearer bk_YOUR_KEY"
You need an API key. Create one under Settings → API. It is free on every plan.
Put your key in an environment variable, add the server to ~/.codex/config.toml, then run codex mcp list to check it.
export BILLINO_API_KEY=bk_YOUR_KEY # ~/.codex/config.toml [mcp_servers.billino] url = "https://api.billino.io/mcp" bearer_token_env_var = "BILLINO_API_KEY"
You need an API key. Create one under Settings → API. It is free on every plan.
Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json for one project. Set BILLINO_API_KEY in your environment.
{
"mcpServers": {
"billino": {
"url": "https://api.billino.io/mcp",
"headers": {
"Authorization": "Bearer ${env:BILLINO_API_KEY}"
}
}
}
}You need an API key. Create one under Settings → API. It is free on every plan.
Add this to .vscode/mcp.json. VS Code asks for your key the first time it connects.
{
"inputs": [
{
"type": "promptString",
"id": "billino-key",
"description": "Billino API key",
"password": true
}
],
"servers": {
"billino": {
"type": "http",
"url": "https://api.billino.io/mcp",
"headers": {
"Authorization": "Bearer ${input:billino-key}"
}
}
}
}You need an API key. Create one under Settings → API. It is free on every plan.
Run this command with your key.
gemini mcp add --transport http --header "Authorization: Bearer bk_YOUR_KEY" billino https://api.billino.io/mcp
You need an API key. Create one under Settings → API. It is free on every plan.
Any client that supports remote MCP servers over Streamable HTTP works. Use these values:
https://api.billino.io/mcpAuthorization: Bearer bk_YOUR_KEYSend your API key as Authorization: Bearer followed by the key. Billino’s sign-in works with Claude; for other clients, use an API key.
“Which invoices are still unpaid?” is a good first request.
One tool per action. Tools that cannot be undone are marked, so a client can ask you before running them.
API keys and MCP share one monthly allowance: 300 calls on Free, 5,000 on Plus. Both plans are limited to 100 calls per minute. Using the Billino app itself is never counted.
Need more? Contact us
Any client that supports remote MCP servers over Streamable HTTP. Claude connects with a sign-in from its directory. For other clients, an API key is the reliable route.
Yes, a free one. Register at billino.io/register, then connect your client.
Yes, on every plan, within the monthly allowance: 300 calls on Free, 5,000 on Plus.
Billino, not the AI. The same rules and legal wording as in the app apply, based on your setup and your client’s.
No. Issued invoices are frozen. They can be cancelled with a linked cancellation document or partly credited. Only drafts can be deleted.
For OAuth connections, open Connected apps in your Billino settings and choose Revoke; access ends immediately. API keys can be revoked in Settings → API.
Free on every plan. Copy the URL once, then just ask.