Connecting an AI Assistant

Connect an MCP client to let your AI assistant work with Maeve content. The hosted server address is:

https://api.maevesocial.com/mcp

You need organization Owner or Admin access, or a Manager role for the workspaces you want to connect. Open Settings > Developer > MCP for the setup instructions and copy buttons for your client.

Add Maeve to Your Client

Claude Code

Run this in your terminal:

claude mcp add --transport http maeve https://api.maevesocial.com/mcp

Then run /mcp in Claude Code, select maeve, and start the browser sign-in.

Codex

Add this entry to ~/.codex/config.toml:

[mcp_servers.maeve]
url = "https://api.maevesocial.com/mcp"

Then run:

codex mcp login maeve

Complete the approval in your browser.

Cursor or Another MCP Client

For Cursor, add this server to .cursor/mcp.json:

{
  "mcpServers": {
    "maeve": {
      "type": "http",
      "url": "https://api.maevesocial.com/mcp"
    }
  }
}

Use the client's authentication action to sign in. Other clients need support for a remote Streamable HTTP MCP server and Maeve's browser authentication flow. Their configuration format may differ.

Approve Workspace and Tool Access

1. Sign into Maeve in the browser window opened by your client.
2. Select the organization and workspaces the assistant needs.
3. Open Choose specific tools and review the selected groups.
4. Approve the connection and return to your AI client.

app.maevesocial.com

claude.ai wants to connect to Maeve Social

Organization

Brie Group

Workspaces

All workspacesBrie PatisserieNorthside DentalHarbour Gym

Tools

All Maeve toolsDone

Content workflowRead content, write drafts, schedule posts, and request review.Publish and deleteEverything in Content workflow, plus publish, retry, archive, and delete. Each one checks with you first.Media RoomView, upload, and organize files.AnalyticsRead your numbers. Nothing changes.Inbox automationSet up keyword auto-reply rules. New rules start switched off.Smart discoveryPulls in tools only as a task needs them.

ApproveDeny

As it arrives: every group ticked, publishing included.

All groups start selected. Clear any groups you do not want the connection to use.

The default selection of all groups also includes task-board writes. A manually restricted selection can leave task tools read-only.

Check the Connection

Ask the assistant to list the Maeve workspaces it can access. Check that the result includes the intended workspace, then ask it to list that workspace's connected accounts.

For a first task, ask it to create a draft for a named account. Have it check platform requirements first and return the saved draft's Open in Maeve link. Review the draft in the app before scheduling it.

If a tool is unavailable, check the connection's approved groups and your plan. Some operations, including review decisions and direct inbox replies, are not available through MCP. See What You Can Automate.

Add the Optional Maeve Plugin

The plugin adds instructions for using Maeve, including checking account capabilities and creating drafts by default. It does not replace MCP sign-in.

In Claude Code:

/plugin marketplace add jared-james/maeve-agent
/plugin install maeve-agent@maeve-agent
/reload-plugins

Invoke the skill with /maeve-agent:maeve-social-scheduler when you want it applied to a task.

In Codex, add the marketplace:

codex plugin marketplace add jared-james/maeve-agent

Open /plugins to install the plugin, then invoke $maeve-social-scheduler.

Connect with an API Key

For an unattended client or one without browser authentication, use a workspace-scoped API key as the bearer token. Store it in the client's environment, not in a committed configuration file.

Codex can read it from an environment variable:

[mcp_servers.maeve]
url = "https://api.maevesocial.com/mcp"
bearer_token_env_var = "MAEVE_API_KEY"

API-key authentication does not show the browser tool-group picker. The key's workspace grants and creator permissions apply, but it can reach the MCP tool surface without that additional group restriction. High-risk tool confirmation requirements still apply.

Review or Revoke a Connection

1. Open Settings > Developer > MCP.
2. Find the client connection and review its workspaces, permissions, and last use.
3. Revoke it if you no longer want that client to have access.

To change the approved workspaces or groups, revoke the connection and approve a replacement. There is no edit action for an existing grant.

Access tokens last six hours. A compatible client refreshes them automatically using a rotating refresh token, which expires after 90 days without renewal. A Refresh only status can mean the access token expired while the refresh token is still valid; it does not necessarily mean the connection is broken.

There is a limit of ten unrevoked connections per person. Revoke old or expired connections before creating more.