AI Connector, MCP & CLI
Boost productivity and focus on what matters. Your AI chats now have their own back office.
Included in every plan. 7 days free, card required.
Connect Claude or ChatGPT in three steps. About as long as it takes to read this section.
- 1
Add Backbone in Claude or ChatGPT
Copy the address from Settings › Integrations and add it as a custom connector. Listings in the Claude and ChatGPT connector directories are on the way.
- 2
Sign in and pick a workspace
Backbone shows what the AI may do and what it can't. One click on Allow, and it works as you.
- 3
Ask, like you would a colleague
The result lands in Backbone right away, in the same place you would have put it by hand.
What you can ask. Almost everything you do in the app works from the chat, in English or German.
“Log 2 hours for the Nordlicht brand workshop yesterday.”
A time entry on Nordlicht GmbH › Brand workshop, marked as added from Claude.
“Draft the September invoice for Kinetik Studio from my hours.”
A draft with the open hours as lines, at the client's rate. You send it.
“Who still owes me money?”
Four open invoices, €12,001.00 in total, the oldest first.
“Send Fernweh Reisen a friendly reminder.”
A reminder for RE-2026-0117, waiting for your OK in the chat.
“Which receipts are still missing for September?”
The card and bank payments without a receipt, with date and amount.
“How many hours did we spend on Hafen Coffee this month?”
Hours per person and project, from the team's timesheets.
You stay in control. The AI works as you, never as more than you.
- It signs in as you, so your role applies
- Anything that leaves your workspace waits for your OK
- The owner can switch AI connections off
- Password, billing and bank connections stay in the app
mcp --for developers
Backbone in your editor. One command for Claude Code, one config block for every other MCP client.
The connector is a remote MCP server over Streamable HTTP. Add it to Claude Code, Cursor or any client that speaks MCP, sign in once in the browser, and your agent can log time, draft invoices or check open payments while you code.
Add the server
In Claude Code it is one command. Other clients take the same address in their
mcpServersconfig.Sign in with OAuth
Run
/mcpin Claude Code (or your client's sign-in button), log in to Backbone in the browser and press Allow. No API keys to create, copy or leak.Call the tools
Your agent sees the same tools as the app. Reads run straight away; anything that sends, deletes or issues comes back as
needs_confirmationand waits for your yes.
claude mcp add --transport http backbone https://back-bone.io/api/mcp{ "mcpServers": { "backbone": { "type": "http", "url": "https://back-bone.io/api/mcp" } } }
Project config for Claude Code. Cursor reads the same mcpServers block from .cursor/mcp.json; no token or header needed, sign-in is OAuth.
// example · → tools/call { "name": "log_time", "arguments": { "client_id": "Nordlicht GmbH", "project_id": "Brand workshop", "date": "2026-09-27", "minutes": 120, "note": "Brand workshop with the Nordlicht team" } } // ← result { "isError": false, "structuredContent": { "created": true, "entry": { "entry_date": "2026-09-27", "minutes": 120 } } } ✓ in your week view, marked as added via MCP
// example · → tools/call { "name": "send_reminder", "arguments": { "document": "RE-2026-0117" } } // ← nothing sent yet: it waits for you { "structuredContent": { "status": "needs_confirmation", "pending_action_id": "pa_3f9c…", "summary": "Send a reminder for RE-2026-0117 to Fernweh Reisen?" } } // → only after you said yes { "name": "confirm_action", "arguments": { "pending_action_id": "pa_3f9c…" } }
Example calls with sample data. Real tool names; your client shows the exact input schema of every tool.
And a CLI. Coming soon
The same tools from your terminal and your scripts, without an AI in between. Log time from a git hook, list open invoices in CI, upload a folder of receipts. Until it ships, MCP in Claude Code does the same jobs.
backbone time log "Nordlicht GmbH" "Brand workshop" 2h backbone invoices list --status open backbone receipts upload ./september/*.pdf
The full tool set, both ways. The connector and MCP get the same tools as the app. Every function works three ways.
In the app
Click it. Every screen in Backbone, as you know it.
In Claude and ChatGPT
Ask for it. The connector, for everyday work in the chat apps.
In your coding tools
Script it. MCP in Claude Code, Cursor and other clients.
Time
Log, fix and report hours, or run the timer.
log_timelist_time_entriestimer_startlist_unbilled_timeClients & projects
Find, add and update clients, budgets and projects.
list_clientscreate_clientset_client_budgetcreate_projectInvoices & quotes
Draft from your hours, issue, send and mark as paid.
create_documentadd_time_to_documentsend_documentmark_document_paidDunning
See who is late, preview and send reminders, pause them.
list_dunningpreview_remindersend_reminderset_dunning_pauseReceipts & bookkeeping
Upload, match and export for your bookkeeper.
upload_filelist_transactionsrun_matchingcreate_exportReports
Hours, revenue, profitability and utilization.
report_hoursreport_revenuereport_profitabilityTeam
See the team, invite people, set weekly targets.
list_teaminvite_memberset_weekly_targetSettings
Company details, numbering, e-mails and templates.
get_settingsupdate_companyupdate_numberingupdate_reminder_settingsA few things stay in the app, on purpose. Changing your password or e-mail, deleting your account or a workspace, handing over ownership, billing and checkout, giving your bank consent and creating a workspace. Changing bank or payment details from the chat needs your confirmation, and the owner gets an e-mail about it.
Same plan, same limits. The connector and MCP are included in every plan. Invoices and receipts you create through them count toward your plan's limits, exactly as if you had made them in the app.
Connector, MCP and CLI questions
Claude and ChatGPT, through the custom connector address in Settings › Integrations. For developers, Claude Code, Cursor and other MCP clients through MCP. Listings in the Claude and ChatGPT connector directories are on the way.
Yes. Both use the same tools as the app, so every function works in the app, in the chat and through MCP. A short list stays in the app on purpose: password and e-mail changes, deleting your account or a workspace, ownership transfer, billing, bank consent and creating a workspace.
No. You sign in with your Backbone account in the browser (OAuth) and press Allow. There are no API keys to create or store. The Backbone API is coming soon.
Coming soon. A Backbone CLI will run the same tools from your terminal and scripts; the commands on this page are a preview and can still change. Until then, use MCP in Claude Code, Cursor or another MCP client.
No. It can draft, but anything that leaves your workspace, like an invoice or a reminder, waits for your OK in the chat. Changing bank or payment details also needs your confirmation, and the owner gets an e-mail.
Only what your role in the workspace allows, because it signs in as you. A member who doesn't see invoices in the app doesn't see them through the AI either.
Yes. The owner can switch AI connections off in Settings › Integrations, and anyone can revoke an app they connected.
Yes, in every plan. Invoices and receipts you create through the connector or MCP count toward your plan's limits, like work in the app. Your AI tool's own subscription is separate.
The Model Context Protocol, an open standard AI tools use to work with other apps. You don't need to know it to use the connector in Claude or ChatGPT; it is why the same tools also work in your coding tools.