MCP SERVER
A social media MCP server for AI agents, with approval built in
An MCP server lets an AI assistant such as Claude use a product’s tools through the Model Context Protocol. Growfinch’s MCP server lets an assistant list your businesses and accounts, check and create campaigns, fill queues and read post results. It cannot approve: where a business requires approval, a person decides in the console.
Updated 22 October 2026 · Growfinch
The Model Context Protocol is an open-source standard for connecting AI applications to external systems. With it, Claude or another MCP client can work in Growfinch for each business you post for.
An MCP server on a social media scheduler is common now. Of the 15 social media tools we checked on 22 October 2026, 11 offer an official MCP server. What Growfinch adds is the combination around it: several businesses kept apart in one console, each with its own accounts and rules, and an approval that only a person in the console can give.
What the assistant can do
The server offers 21 tools. Each has a kind that says how far it can reach:
- Read-only: reads and changes nothing.
- Creates draft: adds content, a file or a queue to one business; what happens next is that business’s rule.
- Policy-controlled: changes something that exists; the business’s policy decides whether the change is allowed.
- Needs permission: only a person can do it, in the console. An assistant is always refused.
| Tool | Kind | What it does |
|---|---|---|
| list_businesses | Read-only | The businesses this key may act on, with each one’s publishing policy. |
| list_connections | Read-only | A business’s connected accounts: platform, handle, status, scopes and token expiry (never a token), and each platform’s limits. |
| list_templates | Read-only | A business’s content templates. |
| validate_campaign | Read-only | A dry run of a campaign: the checklist, a preview per platform and what would happen to it. |
| get_campaign | Read-only | A campaign with its posts and history. |
| list_pending_approvals | Read-only | Items waiting for a person. |
| list_recent_posts | Read-only | A business’s recent posts with status, links and the latest views, likes and comments. |
| get_usage | Read-only | Posts published this month, per business. |
| get_post_metrics | Read-only | Daily snapshots per post and 7- and 30-day totals for one business. |
| list_queues | Read-only | A business’s queues with their slots, mode and whether they are paused. |
| plan_queue | Read-only | Which item lands in which slot over the coming days, the first empty slot and how many days of content remain. |
| create_campaign | Creates draft | A campaign for one business. It waits for a person’s approval unless the business allows automatic publishing for its kind of post. |
| register_media | Creates draft | Registers an image or video by its SHA-256 fingerprint before a campaign uses it, and returns where to upload it. |
| complete_media | Creates draft | Confirms the upload arrived and marks the file ready. |
| create_queue | Creates draft | A weekly timetable for one business: weekday and time slots, accounts, approval mode, order, recycling and a daily maximum. |
| add_to_queue | Creates draft | Adds content without a time to a queue. In a queue that needs approval it waits for a person; the reply says which slot it will take. |
| cancel_campaign | Policy-controlled | Cancels a campaign’s pending posts. |
| update_queue | Policy-controlled | Changes a queue’s slots, accounts, mode, order, recycling, daily maximum or expiry. |
| shuffle_queue | Policy-controlled | Shuffles the items not yet scheduled. |
| pause_queue | Policy-controlled | Pauses or resumes a queue. A paused queue fills no slot; posts already scheduled still go out. |
| approve_campaign | Needs permission | Always refused to an assistant: only a person approves, in the console. |
What it can never do
Three limits hold whatever the prompt says:
- Approve. approve_campaign is listed so an assistant knows the step exists; every call to it is refused. Where a business requires approval, nothing the assistant creates is scheduled until a person approves it in the console. Where a business allows automatic publishing for a kind of post, a person set that rule, and anything outside it still waits.
- See another business’s data. A key is made for named businesses. Every call names its business; Growfinch never guesses it, and a business outside the key’s list answers “no access”.
- Read tokens. Growfinch encrypts each account’s access tokens and never shows them. list_connections returns the handle, status and expiry, never the token.
None of the 21 tools changes a business’s publishing policy or makes keys either. Those stay in the console.
Most marketers agree that a person should review AI-written content first:
Connect Claude to the social media MCP server
Available to early-access members. MCP keys come with early access: when your team joins, we make an API key for the businesses your assistant may act on.
Every client needs three things:
- The server address: https://growfinch.com/api/mcp
- The transport: Streamable HTTP, the MCP transport for remote servers.
- The key, sent with each request in the Authorization header as Bearer followed by the key.
Claude Code
One command adds the server, in the form Claude Code’s MCP documentation gives for remote HTTP servers with a bearer token:
claude mcp add --transport http growfinch https://growfinch.com/api/mcp --header "Authorization: Bearer YOUR_KEY"
Claude’s apps
Add a custom connector with the server address and put the key under its request headers. On Pro and Max plans that is Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors. Claude’s help page on custom connectors has the steps.
Other MCP clients need the same address and key. To check the connection, ask the assistant to list your businesses: it should show only the ones your key was made for.
Example: a week of posts for two businesses
The businesses and posts here are example data. You ask Claude to plan next week for Northwind Coffee and Brightline Studio from a page of notes.
- list_businesses: Claude sees both businesses. Each requires approval before anything is published.
- list_queues: Northwind has a weekday queue at 09:00; Brightline posts on Tuesdays and Thursdays.
- validate_campaign for each post: the Instagram account is connected, the caption fits, and the post will wait for approval.
- add_to_queue: each post joins its own business’s queue, and the reply names the slot it will take.
- plan_queue: Claude shows you the week: planned slots, slots waiting for approval and the first empty slot.
Nothing is public yet. In Approvals, each item shows its business, the platform of every post and its slot. You approve or reject; approved items take their slots. Had the key been made for Northwind only, the calls for Brightline would have been refused.
Security
- Keys per business. Each key is made for the businesses it may act on, and the database keeps each business’s data apart with row security.
- Hashed keys. Growfinch stores a hash of each key, not the key.
- Encrypted tokens. Account tokens are encrypted with AES-256-GCM and never shown, to you or to an assistant.
- An audit log. Every change made through a key is recorded with the key that made it, next to who approved and what was published.
- A kill switch. One switch in Settings stops every external effect, whatever a key or an assistant asks.
- The same rules everywhere. The MCP server goes through the same services and policy checks as the console and the REST API, so an assistant gets no shortcut.
Read next: how approval works per business, AI agents with human approval, and Growfinch for agencies.
Questions
What is a social media MCP server?
A server that lets an AI assistant such as Claude use a social media tool through the Model Context Protocol, an open-source standard for connecting AI applications to external systems. Growfinch’s lets an assistant read your businesses, accounts and results, create campaigns and fill queues; approval stays with a person.
Can Claude post to Instagram or LinkedIn through Growfinch?
Claude can prepare and queue posts for connected Instagram professional accounts, X accounts and YouTube channels. LinkedIn is next. For a business that requires approval, a post goes out only after a person approves it in the console.
Can the AI approve its own posts?
No. The approve_campaign tool is refused to every assistant and every API key. Only a person approves, in the console.
Do I need to write code?
No. You need the server address and a key. Claude Code adds both with one command; in Claude’s apps you add a custom connector and put the key in its request headers.
How do I get a key?
Keys come with early access. Join the list on this page; when your team is onboarded, we make a key for the businesses your assistant may act on.
Is Growfinch listed in MCP directories?
Not yet: for now, keys come with early access.