Agents and MCP

Use GrowedditX from Claude, Cursor or ChatGPT

Last updated 21 October 2026. Checked against the MCP specification revision 2025-06-18.

GrowedditX runs a remote MCP server. Connect it to an AI assistant and the assistant can read your workspace, write drafts in your voice from your brand bank, and queue a post for publication once a person approved it in GrowedditX and you confirm it. It cannot comment, like, send messages or connection requests, or follow anyone, because no such tool exists.

Set it up

The server address is https://growedditx.7hs.site/api/mcp. Clients that support OAuth (Claude and ChatGPT) open a GrowedditX page where you pick the workspace and what the assistant may do. Clients that take a header use an API key: an owner or admin creates one in Settings, Connections, API and agents. A key is shown once; we keep only a fingerprint of it.

Claude (web and desktop)In Claude, open Settings, then Connectors, and add a custom connector with this URL. Claude opens GrowedditX to ask which workspace and scopes to allow. No key to paste. (OAuth)
https://growedditx.7hs.site/api/mcp
Claude CodeRun this in a terminal. Leave out the header to sign in with OAuth from /mcp instead. (API key)
claude mcp add --transport http growedditx https://growedditx.7hs.site/api/mcp --header "Authorization: Bearer gx_live_YOUR_KEY"
CursorAdd this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project), then turn the server on in Cursor's MCP settings. (API key)
{ "mcpServers": { "growedditx": { "url": "https://growedditx.7hs.site/api/mcp", "headers": { "Authorization": "Bearer gx_live_YOUR_KEY" } } } }
ChatGPT developer modeTurn on developer mode in ChatGPT's connector settings, create a connector with this URL and choose OAuth. ChatGPT opens GrowedditX to ask which workspace and scopes to allow. (OAuth)
https://growedditx.7hs.site/api/mcp

The tools

Each tool belongs to one scope: read, draft or schedule. A credential sees only the tools its scopes allow, and it acts as the member who created it, so that member's role still applies. If a member leaves the workspace, their keys stop working.

Read

Look, never touch. Available to every member's credential.

get_workspaceThe workspace this credential belongs to: name, offer, timezone, your role, the credential's scopes, this month's writer allowance and the connected LinkedIn and X accounts (their ids are what schedule_draft takes).
list_spacesThe content spaces in the workspace (a person, a product, a service or a content brand), each with its goal and weekly cadence. Drafts are written for a space.
get_space_briefOne space in full: positioning, audience, pillars, proof, rules, call to action and the memories the writer keeps for it.
search_brand_bankSearch the brand bank: the author's stories, facts, opinions, case studies, objections, offers and writing samples. Each item says whether a person approved it; only approved items reach the writer.
list_draftsDrafts in the workspace, newest first, with status, revision and the first 280 characters. By default lists draft, awaiting_approval and approved.
get_draftOne draft in full: text, status, revision, format, the review notes from the run that wrote it and any queued publication.
list_campaignsCampaigns in the workspace with their playbook, goal, start date, length and how many beats are done.
get_campaignOne campaign in full: every beat (day, network, kind, format, brief, done or not, drafts, captured engagement), the check ins and the people who asked for the lead magnet.
list_scheduledPosts queued for publication, soonest first, with the account and time. Each has the job_id cancel_scheduled takes.
get_results_summaryThe post ledger for a period: what each published post started (comments, people, conversations, leads) as recorded in GrowedditX. Numbers are what the app captured, not network analytics.
list_engage_queueConversations worth replying to from the last seven days: replies to the author's posts and, on plans with the engage queue, the other posts the workspace saved or was alerted to. Use draft_reply for text; the person replies themselves.
list_peopleSearch people saved in the workspace by name, headline or company, optionally by pipeline stage.
get_personOne person: profile link, headline, company, stage, notes, tags and their latest activity captured in the workspace.

Draft

Write into the workspace. Nothing leaves it. Tools marked with a writer run count against the monthly allowance.

create_draftWrite a new draft with the GrowedditX writer for a space and network, from a brief and an optional angle. Uses the brand bank, the space brief and the author's voice, saves the draft in the workspace and returns it with a readiness check. Counts one writer run. Nothing is published. Writer run.
rewrite_draftRewrite a draft with a preset or your own instruction and return the new text. With save: true the text becomes the draft's next revision (earlier revisions are kept and the draft goes back to draft status, so a person has to approve it again before it can be scheduled). Saving needs an editor or above at the moment it saves. Approved and scheduled drafts are never changed. Counts one writer run. Writer run.
add_brand_bank_itemAdd a story, fact, opinion, case study, objection, offer or writing sample to the brand bank. It is saved unapproved: the writer uses it only after a person approves it in GrowedditX.
write_campaign_beatWrite the draft for one campaign beat. The beat decides the network, format and brief; the campaign's context and what worked on earlier beats go to the writer. Counts one writer run. Nothing is published. Writer run.
draft_replyDraft three replies to one engage queue item in the author's voice and return them as text. Nothing is posted: the person copies one and replies on the network themselves. Counts one writer run and respects the daily engagement limit. Writer run.

Schedule

Queue or cancel a publication. Only owners and admins can grant this scope. An agent schedules only drafts a person approved in GrowedditX, and asks the person to confirm each one.

schedule_draftQueue a draft for publication on a connected account at an exact time. An agent can only schedule a revision a person already approved in GrowedditX. If nobody has approved this revision, the call schedules nothing: it sends the draft for approval with your account and time attached and returns status awaiting_approval, the message Waiting for a person to approve in GrowedditX and an approve_url. Tell the person; when an owner or admin approves it there, it is scheduled for that account and time. If a person already approved it, the call without confirm returns a preview with a confirmation phrase: show the preview, and only when they agree call again with confirm: true and confirmation set to that phrase. Needs the schedule scope and an owner or admin.
cancel_scheduledCancel a queued publication before it is sent. The draft stays in the workspace.

The safety model

A person approves first. An agent can only schedule a revision someone approved in GrowedditX, as a teammate or as a client on a review link. For a draft nobody approved, schedule_draft schedules nothing: it sends the draft to Approvals with the account and time the agent asked for, and Approve and schedule there queues it.
Then confirm. For an approved draft, schedule_draft first returns a preview with a confirmation phrase and changes nothing. Only a second call with confirm set to true and that exact phrase queues it. If the draft, the account or the time changes, the phrase changes too.
A saved rewrite is a new revision. It goes back to draft and needs a person's approval again, and saving it needs an editor or above at that moment.
GrowedditX never sends anything on its own. A queued post goes out at the time you confirmed, through the network's official API, from the account you connected. Replies from draft_reply come back as text for you to post yourself.
Brand bank items an assistant adds stay unapproved until a person approves them, so they never reach the writer unseen.
Every call is checked against the credential's workspace and scope and written to the workspace audit log with the actor named as agent and the key or app name.
Revoke a key or a connected app in Settings, Connections, API and agents. It is refused from its next call.

Limits

60 calls a minute and 1,000 an hour per credential; 10 drafting or scheduling calls a minute.
create_draft, rewrite_draft, write_campaign_beat and draft_reply each use one writer run from the same monthly allowance as the app. get_workspace shows what is left. draft_reply also respects the daily engagement limit.
A drafting call answers when the writer has finished and the draft is saved. When the style check asks for a second pass, that can take up to about two and a half minutes.
A workspace holds up to 20 active API keys. OAuth access tokens last one hour and refresh for up to 30 days.
Scheduling needs publishing to be turned on for the network, a connected account and your plan's publishing allowance.

Claude skills

Six Claude skills build on these tools: a weekly plan, a launch week, writing in your voice, a reply round, a campaign report and repurposing a post that worked. Each one drafts and asks before anything is scheduled. Ask support for the skills folder; it comes with install steps for Claude Code and the Claude app.

Sources

Questions about what the extension and the app can do on LinkedIn and X: what the extension can and cannot do.