Customer MCP URLs

Give each of your customers a private URL they can paste into Claude, ChatGPT or Cursor. Their assistant can then use the accounts they connected in your product — and nothing else.

What it is

MCP (Model Context Protocol) is how AI assistants discover and call tools. A customer MCP URL exposes one customer's connected apps as tools for their own assistant.

The URL carries its key, so treat it like a password:

https://api.work.studio/api/v1/workflow/embed/mcp/svx_mk_…

Shown once

The full URL is returned only when you create it. Show it to your customer immediately, and offer to create a new one if they lose it.

From the SDK

getMcpAccess(), createMcpUrl() and revokeMcpUrl() do everything on this page from @workstudio-inc/sdk 0.2.0 or later, if you'd rather not call the endpoints yourself.

What the assistant can do

With that URL, the customer's assistant can:

see which apps they have connected
call operations on those apps, using their own credentials
work with automations you have enabled for them

It cannot reach another customer's connections, your tenant's data, or any app that customer hasn't connected. The key works on the MCP endpoint alone — it is rejected everywhere else in the API.

Check access

GET https://api.work.studio/api/v1/workflow/embed/mcp-key
Authorization: Bearer svx_st_…
X-Embed-Tenant: <your tenant id>

{
  "enabled": true,
  "active": false,
  "keyPrefix": null,
  "endpoint": "https://api.work.studio/api/v1/workflow/embed/mcp"
}

Field	Meaning
`enabled`	You allow assistant access for your customers
`active`	This customer currently has a live URL
`keyPrefix`	The visible start of their key, for display
`lastUsedAt`	When their assistant last called it

Create a URL

POST https://api.work.studio/api/v1/workflow/embed/mcp-key
Authorization: Bearer svx_st_…
X-Embed-Tenant: <your tenant id>
Content-Type: application/json

{}

{
  "url": "https://api.work.studio/api/v1/workflow/embed/mcp/svx_mk_…",
  "key": "svx_mk_…",
  "keyPrefix": "svx_mk_a1b2",
  "endpoint": "https://api.work.studio/api/v1/workflow/embed/mcp",
  "createdAt": "2026-09-15T18:30:00Z"
}

Creating a URL replaces any the customer already had — the old one stops working immediately.

Revoke

DELETE https://api.work.studio/api/v1/workflow/embed/mcp-key
Authorization: Bearer svx_st_…
X-Embed-Tenant: <your tenant id>

Returns 204. The customer's assistant loses access on its next call.

In the catalog

If you include the connections tab in the web component, your customers can create and revoke their own URL without you building anything. The component raises svx:mcp:created and svx:mcp:revoked so you can track adoption.

What your customer does with it

They add the URL to their assistant as a remote MCP server. In Claude Desktop that's Settings → Connectors → Add custom connector; in other clients, wherever remote MCP servers are configured.

A useful onboarding moment

A customer who connects Slack and Jira in your product, then pastes one URL into Claude, can ask their assistant about their own tickets straight away. That is usually the moment the value lands.

Next steps

Web component — surface this in the catalog
Authentication — how MCP keys differ from session tokens

Something not behaving as described? support@work.studio