Skip to main content

Before you start

You need a Studio account. Go to studio.growhub.ai and sign in with Google — a personal studio is created for you on first sign-in.

Add the server

Then run /mcp inside Claude Code and pick studio to complete sign-in.
Any client that speaks streamable HTTP can connect directly to the endpoint. Clients limited to stdio should bridge through npx mcp-remote <url>.

Sign in

The first tool call triggers the OAuth flow:
1

Your client discovers the authorization server

The server answers an unauthenticated request with 401 and a WWW-Authenticate header pointing at its metadata.
2

A browser window opens

You land on studio.growhub.ai/login and continue with Google.
3

You grant consent

Studio issues an access token to the client. It is stored by the client, not by you — there is no key to copy.
See Authentication for the full flow and the endpoints involved.

Verify it works

Ask your assistant:
A fresh studio returns an empty list — that is a successful call. Connect a platform next:
The connect_platform tool returns a URL. Open it, authorize LinkedIn, and ask for list_connections again to confirm.

Write something

Studio creates the draft and returns its url. Open it to review, then:
Ask for a draft first, review the url, then publish. publish_post is immediate and irreversible from Studio’s side — deleting a published post happens on the platform.

Local development

Running the Worker locally? Point the client at your dev server instead:
Local dev uses the same OAuth flow against http://localhost:5173/login.