About 4 min read
Workspace API and MCP (developer overview)
When to use the Workspace HTTP API and Model Context Protocol instead of the UI, with pointers to full technical documentation.
When APIs help
Use the Workspace HTTP API when another system must create tasks, query agents, or react to webhooks. Use MCP when an AI tool host should call your workspace with structured tools.
For live apps you built in Build—with a share link and optional per-app API—see Deploy and share a live app. That uses different keys from the Workspace API.
Relationship to this Help Center
- This Help Center focuses on concepts and operations. Request paths, payloads, scopes, and examples live in the technical documentation.
Canonical documentation
See the Documentation article “Workspace API and MCP” for bearer authentication, routes, webhooks, rate limits, and Streamable HTTP MCP details.
Full API and MCP reference
Continue in Workspace API and MCP (documentation) for routes, examples, scopes, and governance.
Related articles
- What to do right after you sign up — A short checklist after you create an account: confirm email, pick or wait for your workspace, and open the product for the first time.
- Workspaces explained — How a workspace relates to your company account, why you might have more than one, and where your agents and data live.
- Sign in, SSO, and launch links — How sign-in works with the control plane, branded workspace URLs, and secure handoff into your tenant runtime.
- Members, invites, and roles — Inviting colleagues, what new members should expect on first visit, and keeping access aligned with how your team works.
- Billing, plans, and invoices — Where billing is managed, how usage-related charges may appear, and how to get help when something looks wrong on an invoice.
- Help Center home