Your CharmIQ workspace isn't only accessible through the browser. CharmIQ exposes its own MCP servers — the same protocol your Charms use to reach external tools — so external applications can connect inward.

Any MCP-compatible client can connect to CharmIQ. Once connected, it can run completions with your Charms, read and write documents, launch tasks, generate images, and more. The workspace your Charms work in becomes accessible from your terminal, your IDE, or any tool in your stack.

When an external client connects to CharmIQ, it gets access to a set of tools organized by capability:

 tool that describes all available servers.

Your Charms, your documents, your workspaces — all accessible from external tools, with your explicit authorization.

When an external tool connects to CharmIQ, it connects to a specific 

 — the billing and operating context you work within. Credits consumed through that connection come out of that Organization's balance.

If you belong to more than one Organization (a personal account plus one or more Company accounts, for example), you'll choose which one to connect during the authorization step. The token the external tool receives only works for that Organization. If you need a tool to access multiple Organizations, authorize separately for each.

 — How Organizations work, how to belong to more than one and how to switch between them.

Claude Code (Anthropic's CLI tool) supports MCP natively. To connect it to CharmIQ:

From that point, Claude Code can call CharmIQ's MCP tools directly. You can run completions with your Charms, manage documents, and trigger agent tasks — all from the command line.

Copilot within VS Code supports MCP natively. VS Code connects at the individual server level — you pick the server that matches what you need. For most workflows (reading, writing, and searching documents), that's the VFS server.

Once connected, VS Code has full access to CharmIQ's document layer — the same workspace you see in the browser, accessible directly from your IDE. To add other capabilities (Agent, Generation, etc.), repeat the steps above with the corresponding endpoint.

Zapier's MCP support lets you trigger CharmIQ agent tasks from Zapier workflows. A new Zendesk ticket could trigger a Charm to draft a response. A new HubSpot lead could trigger a briefing document. Any event in any of Zapier's thousands of connected apps can kick off a CharmIQ workflow.

Setup follows the same OAuth pattern: Zapier connects to CharmIQ's authorization endpoint, you consent and select which Organization to connect, and Zapier receives a scoped access token.

If you're building a custom application that needs to connect to CharmIQ, CharmIQ implements OAuth 2.1 with Dynamic Client Registration and standard discovery endpoints.

 parameter, all scopes it's allowed to have are granted by default.

 PKCE is mandatory for all authorization requests (S256 only). Organization Owners can create scoped OAuth clients with a client secret for server-to-server integrations that need a confidential client.

 During consent, the user selects which Organization to bind the token to. The resulting JWT carries 

 Access tokens expire after one hour. Refresh tokens expire after 30 days with rotation — each refresh issues a new refresh token. Authorization codes are single-use and expire after 10 minutes.

 — CharmIQ's OAuth implementation is RFC 8414 (Authorization Server Metadata) and RFC 9728 (Protected Resource Metadata) compliant. Standard MCP clients that support discovery will find CharmIQ's configuration automatically at:

. Dynamic clients (public, no secret, PKCE required) are cleaned up after 90 days of inactivity.

Every inbound connection is scoped to a specific user and Organization. The access token your external tool receives carries:

A token issued for one Organization cannot access another Organization's resources. If you're a member of multiple Organizations, you authorize each connection separately.

You can revoke any inbound connection from CharmIQ's authorization settings. Organization Owners can also revoke Organization-wide client access.

 — How inbound, outbound, and Application connections fit together.

 — How Organizations work and how to switch between them.

 — Organization Owners: how to create Organization-scoped OAuth clients for custom integrations.

 — Authenticating with external APIs from inside a custom CharmIQ Application.

How to connect Claude Code, VS Code, Zapier and custom applications to your CharmIQ workspace via MCP and OAuth.

Capability	What It Does	Endpoint
Agent	Run completions with your configured Charms; list available Charms	`/mcp/agent`
VFS (Virtual File System)	Create, read, update, delete and search documents	`/mcp/vfs`
Chat	Create and manage Chat documents; run completions with Charms	`/mcp/chat`
Collections	Manage document collections	`/mcp/collection`
Docs	Browse and read CharmIQ documentation	`/mcp/docs`
Generation	Generate images, video, audio and music	`/mcp/generation`
Usage	Query usage records, credits and limits	`/mcp/usage`

Scope	Access
`richtext.read`	Read documents, Charms, chats, collections
`richtext.write`	Create, update, delete documents and related resources

Endpoint	URL
Authorization	`https://api.charmiq.ai/oauth/authorize`
Token	`https://api.charmiq.ai/oauth/token`
Dynamic Client Registration (RFC 7591)	`https://api.charmiq.ai/oauth/register`
User Info	`https://api.charmiq.ai/oauth/userinfo`
Server Metadata	`https://api.charmiq.ai/.well-known/oauth-authorization-server`
Resource Metadata	`https://api.charmiq.ai/.well-known/oauth-protected-resource`

Connecting External Tools to CharmIQ

CharmIQ as a Service

What External Tools Can Do

Organizations and Billing Context

Connecting Claude Code

Connecting VS Code with Copilot

Connecting Zapier

Building a Custom Integration

Authorization and Access Control

Patterns

Next Steps