Workspaces

ContextPie has two layers of tenancy. An organization is the billing entity — one per customer, with a single subscription. Inside it live one or more workspaces, and a workspace is what actually owns skills. Everything an agent touches is scoped to a workspace.

Organization vs workspace

People are added once at the organization and then granted access to individual workspaces. A member only sees the skills in the workspaces they belong to.

Each workspace has its own endpoint

A workspace's slug addresses its MCP endpoint directly:

https://mcp.contextpie.com/w/your-workspace

Connecting an agent to that URL exposes only that workspace's skills — nothing from other workspaces or other orgs. The slug is generated from the workspace name but you can edit it under Settings → Workspace (it's checked for uniqueness). Changing it changes the endpoint, so any connected clients need their config updated.

Because the workspace lives in the URL, the same account can connect one agent to /w/platform-team and another to /w/support and each stays cleanly scoped.

Keys and people are workspace-scoped

• API keys are created per workspace and only reach that workspace's skills — see Connecting an agent.
• Members are managed at the org (Members), with a per-person workspace-access editor. Assign someone to one workspace or several.
• Analytics are per workspace: the dashboard reflects the traffic for the workspace you're viewing.

When to use more than one

Use separate workspaces to keep discovery and telemetry cleanly divided — for example one per team, per product, or per environment (a staging workspace that never pollutes production's numbers). Every new organization starts with a default workspace, so solo users never have to think about this. Creating additional workspaces is gated by your plan; see Pricing.

Next: Authoring a skill.