This is the powerful AI: you connect your own Claude to Onebase, so it actually reads and works in your data — "show me my open projects", "draft a quote for Marte", bulk clean-up across customers. This is a completely different thing from the in-app help bot, which can't see your data (see the Onebase assistant).
The connection runs over MCP (Model Context Protocol). You add Onebase as a custom connector in Claude — one click to sign in, no keys to paste. The connector acts as you: same roles, same access, same tenant. You'll need a Claude subscription and a few minutes.
The two URLs
Add Onebase as a custom connector in Claude — one-click sign-in, no keys. The read connector exposes queries; the write connector exposes changes:
- Read (queries) — https://onebase.no/api/mcp-read
- Write (changes) — https://onebase.no/api/mcp-write
If you only want Claude to read — never change anything — add only mcp-read. Then no write tools are visible at all.
How to connect
- Open Claude.
- Go to Settings → Connectors → Add custom connector.
- Paste https://onebase.no/api/mcp-read (or https://onebase.no/api/mcp-write).
- Choose Connect and approve the one-click sign-in (OAuth — no key to paste).
- Claude auto-discovers the tools Onebase exposes — the whole business surface, from customers and projects to time tracking and HR (minus what's blocked; see "Honest about the limits").
- Try it right away: ask "list my open projects".
Good to know
- Writes are audited. Every change Claude makes through the write connector is logged with source "mcp" and shows up live in Onebase, just like the rest of your work.
- Read-only if you want. Add only mcp-read and Claude can read but change nothing.
- It acts as you. The connector carries your roles, your tenant isolation and your feature gates — it sees no more than you do.
- Alternatives. If you'd rather use a REST API or a stdio MCP package, you'll find those and a "try it" reference at /api/v1/docs. API keys are minted in-app under Settings → API keys.
Honest about the limits
- Some things stay blocked, whatever your role. Platform administration, billing, privacy tooling (export, DSAR, erasure) and API keys are not exposed as tools — nor is the help assistant itself. The same goes for a handful of irreversible actions: transferring ownership, removing a member, deleting your own account, and GDPR-erasing a contact. Those stay in the browser.
- Special categories are not technically blocked. Claude does what you can do — including in HR and sick leave. You decide what gets asked, and you hold the lawful basis. See AI & your data.
- The data is retained at Anthropic. The MCP connector does not run with zero data retention — what Claude pulls from Onebase sits with Anthropic under their standard retention. Ask narrowly.
- You'll need your own Claude subscription, and the connection takes a few minutes the first time. After that, Onebase is just a connector Claude remembers. Onebase doesn't charge extra for this — it's your Claude talking to your Onebase.