Skip to main content
Fabl runs a Model Context Protocol (MCP) server, so an AI assistant such as Claude can work in your organization for you: find pages, fill in fields, build components and templates, write automation rules and workflows, and run a rundown. You connect once, sign in with your Fabl account, and the assistant then acts as you, with your permissions.

Server address

The server uses the Streamable HTTP transport. You don’t need an API key: the first time your assistant connects, it opens a browser window where you sign in to Fabl and approve access.

Connect Claude

1

Add a custom connector

In Claude, open Settings → Connectors and choose Add custom connector.
2

Enter the server address

Name it Fabl and paste https://api.fabl.studio/mcp as the URL.
3

Sign in to Fabl

Choose Connect. Sign in with your Fabl account in the window that opens and approve access.
To check the connection, ask your assistant “Who am I in Fabl?”. It answers with your name, the organization it is working in, your role and your permissions.

What the assistant can do

The assistant acts as you in your organization. Every tool checks your role and permissions before it runs, so the assistant can only do what you could do in the app. If you can’t delete a rule in Fabl, neither can your assistant. What it can reach:
  • Content: spaces, folders, pages, fields, components, templates, field presets and tags
  • Media: search the library and add media to pages
  • Feeds: browse followed feeds and import their items
  • Automation: rules, devices, device types, agents and integrations
  • Workflows: build workflows, run them and follow their runs
  • Live production: start and stop a rundown, cue items and take them to air
See MCP tools for the full list.

When Claude asks for approval

Every Fabl tool tells your assistant whether it only reads or whether it changes something:
  • Read-only tools (listing, getting and searching) can run without asking you each time.
  • Tools that change anything always ask for your approval first. This includes creating, editing and deleting content, and anything that acts on your studio: testing or triggering a rule, and starting, cueing or taking a rundown.
Claude uses these hints to decide when to ask. Other clients may handle them differently, so check your client’s settings.
Tools that trigger rules or drive a rundown send commands to the real devices behind your agent. Approve them only when your studio is ready for it.

Disconnect

To stop an assistant from working in Fabl, remove the Fabl connector in your client’s settings. In Claude Code, run claude mcp remove fabl.