# AI client setup

Picmim exposes a full remote Streamable HTTP MCP endpoint for compatible AI clients. Follow the steps for your specific client below, or use the endpoint directly with any other Streamable HTTP-capable client.

`https://picmim.com/mcp`

OAuth is the preferred connection method. Sign in to Picmim from the client and choose the workspaces to share. New connections start with every supported capability and automatic execution enabled; owners can later disable capabilities or require approval for every write action. Workspace roles still limit what the connection can actually do.

## ChatGPT

The Picmim connector is rolling out through the OpenAI plugin directory. Until it reaches general availability, you can still connect during private testing.

1. Install the Picmim plugin once it appears in the OpenAI plugin directory.
2. During private testing, add `https://picmim.com/mcp` as a remote MCP server in developer mode instead.
3. Complete the Picmim OAuth flow when prompted.

## Grok and the xAI API

xAI currently documents remote MCP as a developer and API tool rather than a public consumer connector marketplace. Configure the Picmim server in an xAI Responses API request with this tool definition:

```json
{
  "type": "mcp",
  "server_url": "https://picmim.com/mcp",
  "server_label": "picmim",
  "server_description": "Plan, create, schedule, publish, and analyse social content in consented Picmim workspaces."
}
```

Supply a protected Picmim personal token through xAI's `authorization` field at runtime, or use another xAI-supported protected header mechanism, and never commit the token to source control. In the OpenAI-compatible Responses API, restrict `allowed_tools` when your application only needs part of the Picmim catalog; the native xAI SDK calls the same option `allowed_tool_names`.

## Muse Code

Add Picmim as an enabled user-settings Streamable HTTP server:

```json
{
  "schema_version": 1,
  "mcpServers": {
    "picmim": {
      "type": "streamable-http",
      "url": "https://picmim.com/mcp",
      "enabled": true,
      "required": false,
      "startup_timeout_sec": 30,
      "tool_timeout_sec": 900
    }
  }
}
```

Then run `muse mcp login picmim` and complete Picmim OAuth in the browser. OAuth login applies to user-settings remote servers, so do not add a static header when using this flow.

## Claude

For the public Claude Connector Directory submission, use the social-design endpoint `https://picmim.com/mcp/claude-directory`. It keeps Picmim planning, visual design, scheduling, publishing, inbox, media, settings, and analytics capabilities, but only exposes AI visuals as social-post, story, campaign, and content-plan design workflows through `manage_social_visuals` and `start_social_visual_operation`.

1. For an elevated custom Claude connector with the unrestricted Picmim catalog, open Settings > Connectors in Claude instead.
2. Enter `https://picmim.com/mcp` as the connector URL.
3. Complete OAuth to finish connecting.

## Cursor

Add this remote server to the Cursor MCP configuration:

```json
{
  "mcpServers": {
    "picmim": {
      "url": "https://picmim.com/mcp"
    }
  }
}
```

Start the server from Cursor MCP settings and complete OAuth when prompted.

## Gemini CLI

Add this server to Gemini CLI settings:

```json
{
  "mcpServers": {
    "picmim": {
      "httpUrl": "https://picmim.com/mcp"
    }
  }
}
```

Run the Gemini CLI MCP authentication command for `picmim` and finish the browser-based OAuth flow.

## VS Code and GitHub Copilot

Add this remote server to the VS Code MCP configuration:

```json
{
  "servers": {
    "picmim": {
      "type": "http",
      "url": "https://picmim.com/mcp"
    }
  }
}
```

Start the Picmim server from the MCP view and complete OAuth when prompted.

## Public connector repository

Review the public metadata, platform-specific behaviour, test prompts, and troubleshooting guide at [https://github.com/mckrosekri/picmim-mcp](https://github.com/mckrosekri/picmim-mcp).

## Security

Do not place Picmim credentials in a repository or shared configuration. Use each client's OAuth flow whenever it is available.

Personal tokens are intended only for clients and automation environments that provide a protected secret store.