Skip to main content
Studio is a content studio for creators: one place to write a post, connect the platforms you publish to, and get it out — now or on a schedule. The Studio MCP server exposes that whole loop as Model Context Protocol tools, so Claude, Cursor, or any other MCP client can do it by chatting. There is no API key to manage — your client signs you in with Google over OAuth 2.1 and acts inside your studio, with your permissions.

Connect your client

Add the server to Claude Code, Claude Desktop, Cursor, or MCP Inspector.

How auth works

OAuth 2.1, discovery endpoints, and which studio your tools act on.

Browse the tools

All 16 tools, their inputs, and what they return.

Publish your first post

Connect LinkedIn, write a draft, publish it — end to end.

​
Endpoint

The server speaks streamable HTTP on POST /mcp. Clients that only support stdio can bridge to it with mcp-remote.

​
What you can ask for

Every post the server returns carries a url — a deep link into the web studio. Hand it to the user instead of a bare id so they can see what you wrote.

​
The same functions as the API

MCP is not a wrapper around the REST API — both surfaces call the same typed functions in the Worker. A tool and its matching endpoint validate identically, emit the same analytics, and can never drift apart.
Studio is in active development. Today it publishes text and image posts to LinkedIn and X; video and document publishing is stored but not yet dispatched.