✦Currently in private beta.
Basics

AI Connections (MCP)

Intermediate6 min read

Connect Claude, ChatGPT, Cursor, VS Code, Antigravity, or any MCP-compatible AI client to your QONE workspace — so your AI can read your tasks, invoices, and docs, and take limited actions, all with your permissions.

Key concepts

  • MCP (Model Context Protocol): An open standard that lets AI clients talk to external systems (like QONE) through a structured API.
  • QONE MCP Server: The endpoint your AI client connects to. It reads — and can write — your workspace data, scoped to your user permissions, never more than you can see.
  • Active Client: Each AI application (e.g., "Claude on my laptop", "Cursor at work") shows up as a separate registered client, with its own revocation control.
  • Scopes: What the connected client is allowed to do. There are 9 scopes, including 3 write scopes (projects:write, finance:write, hr:write). A client that requests no scopes is granted all of them by default — review the consent screen and limit your client's config to only what it needs.
  • One token per workspace: The consent screen includes a workspace (tenant) selector; each authorization issues a token scoped to a single workspace.
  • Two places to manage: Your personal list at My Profile > Connections, and the admin-level tenant integration at Settings > Integrations > MCP (for platform-wide setup).
How to

Step-by-step

Revoke a Client

  1. Find the client in the list.

  2. Click Revoke.

  3. The client is removed immediately. Future requests from that app will fail until you reauthorize.

    Use this if:

    • You lose a device
    • An app's behavior changed and you want to cut access
    • You are rotating credentials as a security hygiene habit

Admin: Tenant-level Integration

If you are a workspace admin, you can also see an admin view at Settings > Integrations > MCP. This is the same page layout with the same controls — your personal connections. It exists in Settings so admins can reach it even without navigating through their personal profile.

There is no "workspace-wide" MCP credential — every AI client connects under a specific user's identity. This is intentional: it preserves per-user permissions and gives you a clean audit trail per teammate.

Security Model

  • Your permissions are enforced server-side. The AI client cannot bypass them by asking nicely; QONE rejects any request outside your scope.
  • Connections are per-user, per-device-per-app. Each install is its own credential, and each token is scoped to a single workspace.
  • High-risk actions are permanently blocked via MCP — sending invoices, recording payments, approving expenses or leave, and any delete must go through the web UI.
  • Medium-risk writes use confirmation tokens (preview → confirm), so the AI cannot silently create billable or financial records.
  • Revocation is immediate. Clicking Revoke cuts access in seconds — the client gets an auth error on its next call.
  • Every write is audit-logged with actorType: "MCP" so your admin can see exactly what the AI did, when, and to what.

Troubleshooting

"MCP endpoint not configured" The QONE deployment running your workspace does not expose an MCP endpoint. Contact your admin — they need to set MCP_URL (or the equivalent) in the deployment config.

"Client connects but sees no data" Check that your user role has the expected permissions. If you cannot view, say, invoices in the QONE UI, the AI cannot either.

"Claude asks to authenticate every time" Each Claude install/device is a separate credential. If your Claude Desktop on laptop A works but on laptop B does not, authorize laptop B once from the Connections page.

"I see clients I don't recognize" Revoke them immediately. Each authorization creates an explicit entry — if you see something unfamiliar, someone else may have accessed your account, or an old app lingered.

Tips & best practices

  • Connect client-by-client, only what you actively use. Fewer active clients = smaller attack surface.
  • Review the list every few months. Revoke anything with a stale "Last used" date.
  • Use descriptive names in your AI client so the Active Clients list is self-explanatory.
  • Combine with AI Features. QONE's built-in AI assistant works without MCP; MCP is for connecting your own external AI tools.

Was this article helpful?

Your feedback helps us improve these guides.