> ## Documentation Index
> Fetch the complete documentation index at: https://grow-hub.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Studio MCP

> Draft, schedule, and publish social posts from any MCP client.

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](https://modelcontextprotocol.io) 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.

<CardGroup cols={2}>
  <Card title="Connect your client" icon="plug" href="/quickstart">
    Add the server to Claude Code, Claude Desktop, Cursor, or MCP Inspector.
  </Card>

  <Card title="How auth works" icon="key" href="/authentication">
    OAuth 2.1, discovery endpoints, and which studio your tools act on.
  </Card>

  <Card title="Browse the tools" icon="wrench" href="/tools/overview">
    All 16 tools, their inputs, and what they return.
  </Card>

  <Card title="Publish your first post" icon="rocket" href="/guides/first-post">
    Connect LinkedIn, write a draft, publish it — end to end.
  </Card>
</CardGroup>

## Endpoint

<CodeGroup>
  ```bash Production theme={null}
  https://studio-api.growhub.ai/mcp
  ```

  ```bash Local dev theme={null}
  http://localhost:8787/mcp
  ```
</CodeGroup>

The server speaks **streamable HTTP** on `POST /mcp`. Clients that only support
stdio can bridge to it with [`mcp-remote`](/quickstart#add-the-server).

## What you can ask for

| Area        | Tools                                                                                                  | What it does                 |
| ----------- | ------------------------------------------------------------------------------------------------------ | ---------------------------- |
| Drafts      | `list_posts`, `get_post`, `create_draft`, `update_draft`, `delete_draft`                               | Write and manage post drafts |
| Publishing  | `publish_post`, `schedule_post`, `unschedule_post`                                                     | Post now, or queue for later |
| Media       | `create_upload_session`, `request_asset_upload`, `upload_asset_inline`, `attach_asset`, `detach_asset` | Attach images to a post      |
| Connections | `list_connections`, `connect_platform`, `disconnect_platform`                                          | Link LinkedIn and X accounts |

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.

```
MCP client ─┐
            ├─▶ posts.ts / publish.ts / assets.ts / connections.ts ─▶ D1 + platform adapters
REST / web ─┘
```

<Note>
  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.
</Note>