Skip to main content

Connecting to the Studio MCP

Synced from bicycle-studio-api

Source: studio_guide("mcp") (GET /api/studio/v1/guide/mcp) rendered at origin/platform (1afd83f), synced 2026-09-28. Do not edit this page here; change the source and run yarn sync:studio.

URLs​

  • Preview: https://preview.bicycle.ai/mcp (every toolset except chat). Build and test here.
  • Prod: https://app.bicycle.ai/mcp.
  • One toolset: /mcp/<toolset>, for example /mcp/workflow.

The MCP is stateless: each request is its own connection. Long work returns an id at once; you poll it (invocation_get, workflow_run_describe, agent_result, analysis_result).

Two ways to sign in​

OAuth (Claude connector, claude mcp add without a header)Platform API token
Howthe person consents in the browsera person makes a token (role API) in Bicycle; --header "Authorization: Bearer $TOKEN"
Scopesapps:*; functions:* only where the deployment offers themthe role's scopes, including functions:*
You seedataapp_*, query_*, design_*, analysis_*, workflow_*, agent_*, notebook_*, invocation_*all of those plus function_*, fn_*, wf_*

No function_* tools? Call studio_whoami: it lists the scopes you hold and what to tell the person. A connection keeps the scopes it was given until the person reconnects. tools/list shows only the tools your scopes allow.

Scopes​

ScopeLets you
apps:readread apps, run queries, read workflows and runs, run Detect and Explain and registered agents
apps:writecreate apps and versions; create, change and run workflows
apps:publishpublish apps and workflows (gated changes still need a person)
functions:read / write / publishread, author and test, publish functions (widening publishes need a person)
functions:invokecall fn_* and wf_* tools and read their runs

Toolsets​

PrefixFor
studio_this guide and studio_whoami; always on
dataapp_apps: create, upload, publish, share, schedules, ask an app's chat
query_the semantic catalog and cache-only semantic SQL
design_compose an app from a spec by interview
function_author, test and publish functions of every kind
fn_<name>, wf_<slug>call published functions and workflows exposed to MCP
invocation_read any run: record, events, trace, lists
workflow_build, try, publish and run workflows
agent_run registered Bicycle agents such as cause (agent functions you build are function_*)
analysis_Detect and Explain
notebook_notebooks (not needed for data apps)

Resources and prompts mirror the guides: studio://guide, prompt start-here, studio://skill/workflow, studio://skill/ask-show-ship, studio://skill/semantic-query.

guide_version bb2461328de4