Maeve Social
A hosted MCP server for planning, scheduling, media, analytics, and social publishing.
Documentation

What you can ask it to do
It is not a chatbot bolted onto the side. The agent does the work in your workspace, and you open Maeve to find it done.
It has your connected accounts, your Media Room, your labels and your strategy to work from, so it knows what each network needs before it writes anything.
Things you can ask for
Planning and writing
- Show me everything scheduled next week and point out the gaps.
- Draft five posts for the new collection in our brand voice.
- Adapt this announcement for Instagram, X, Threads and LinkedIn.
- Turn these product photos into content for Instagram and LinkedIn.
- Which drafts are still waiting on media?
The calendar
- Schedule the approved posts for 9am Sydney time.
- Move Thursday's post to Saturday morning.
- What is going out this weekend, and on which accounts?
- Fill next month from the content table I have already written.
Media
- Upload these photos and label them Autumn campaign.
- Find the campaign images in my Media Room and put them in a new folder.
- Which images have we already used this month?
Performance
- Which content performed best last month, and what should we repeat?
- How did Reels do against carousels over the last 30 days?
- Compare our follower growth with the competitors we track.
- Which labels and pillars are pulling the most engagement?
Working with the team
- Send this content to the team for review.
- Create the launch tasks, add checklists and assign them.
- Summarise our strategy goals and bets.
- Create an auto reply for the shipping questions we keep getting.
Two minutes to set up
Install the plugin for your agent, sign in through your browser, and pick the workspaces it can reach. There is no API key to copy and nothing to keep in a config file.
The plugin is open on GitHub, and it carries the instructions that teach your agent how Maeve works, so it checks what a channel supports before it drafts for it.
Install the Maeve plugin
- Claude Code /plugin marketplace add jared-james/maeve-agent then /plugin install maeve-agent@maeve-agent
- Codex codex plugin marketplace add jared-james/maeve-agent then install it from /plugins
- Gemini CLI gemini extensions install https://github.com/jared-james/maeve-agent
- Qwen Code qwen extensions install jared-james/maeve-agent
- Cursor Search Maeve Social in the Cursor marketplace
- Grok Build Search Maeve Social in the Grok Build marketplace
Any other MCP client
https://api.maevesocial.com/mcp
Add the endpoint and use the client's own authenticate action. Every route signs in through your browser, so there is no key to paste anywhere.
You decide how far it reaches
You approve what the connection can do when you connect it, and you can leave publishing and deleting out of it altogether.
Anything public or permanent has to be confirmed by name first, so nothing goes out because an agent misread you. Settings shows every connection and revokes one on the spot.
The assistant surface
In
- Draft and edit content
- Schedule posts
- Media Room, including uploads
- Task board
- Ask for internal or client review
- Read integrations and taxonomy
- Read campaigns and strategy
- Analytics
- Inbox auto-reply rules
Review publishing access before approving
All groups start selected. Clear Publish and delete to remove immediate publishing and deletion operations. Content workflow still allows scheduling, which can publish a post later. High-risk actions require confirmation for the specific target.
Most of what an assistant cannot do is reachable through the CLI or the API instead. Three things are reachable from neither, because they need a signed-in browser.
Questions
What is this?
A connection between Maeve and your AI agent. Once it is set up, the agent can work in your workspace: write content, fill the calendar, organise the Media Room, read your analytics, send things for review and set up inbox auto replies.
Which agents work with it?
Claude Code, Codex, Cursor, Gemini CLI, Qwen Code and Grok Build have a plugin. Anything else that speaks MCP can connect to the hosted endpoint directly.
How do I connect it?
Install the plugin for your agent from github.com/jared-james/maeve-agent, or add the endpoint https://api.maevesocial.com/mcp to any MCP client. Either way you sign in through your browser and approve what the connection can reach. There is no key to paste.
Does it see my real workspace?
Yes. It reads what is actually in Maeve: your drafts, your calendar, your media, your analytics, your strategy. You never paste a screenshot or re-explain your setup.
Can I stop it publishing things?
Yes. You approve groups when you connect, so you can leave publishing and deleting out. Watch one thing: content workflow includes scheduling, and a scheduled post publishes later on its own.
What stops it doing something daft?
Anything public or permanent has to be confirmed by name before it runs, and two deletions can never be auto-confirmed. Reading is open, writing is not.
What can it not do?
Reply to comments and DMs, approve or reject a review, touch ad budgets, move things around the Grid Planner or the Workbench, or generate a PDF report. API keys, member roles and connecting a social account cannot be reached from anywhere outside the app.
Who can set it up?
An organisation owner or admin, or a manager for the workspaces you want to connect. Your own role and plan still apply once it is connected.
Can I see and revoke connections?
Settings, Developer, MCP lists every connection with its workspaces, its permissions and when it was last used. Revoke one and it stops immediately.
Is there an option for a server or a script?
Yes. The public API is the broadest surface, and the CLI covers terminal work and local files. MCP is the one built for an agent in a conversation.