It can discover workspaces, Social Sets, and X, LinkedIn, and Threads publish targets.
It can read current platform text and media limits and prepare target-specific publishTargets.
It can read, create, update, and, when authorized, delete posts, ideas, folders, and media.
Risky actions such as publishing and deleting also require explicit confirmation and the relevant granular scope.

Routines are not yet exposed through Public API or MCP; automated workflows remain private until user ownership and a dedicated permission domain are complete.

Connect to Claude

Set up the Claude connection

For Claude, the XPlanner connection opens Claude’s connector screen with the connection details ready.

Open Account Settings > MCP.
Select the Connect action on the Claude card.
Check the MCP server name and endpoint in the Claude connection screen.
Approve the connection in Claude.

Claude’s connection screen auto-fills the details it supports; if a field is missing, copy the endpoint from the MCP drawer.

Connect to ChatGPT / Codex

Set up the ChatGPT and Codex connection

You can create the connection in the ChatGPT Connector screen using the XPlanner MCP endpoint.

In Account Settings > MCP, select the Connect action on the Codex card.
When the ChatGPT connector screen opens, set the connector name to xplanner.
Enter https://mcp.xplanner.co/mcp in the MCP endpoint field.
Complete the XPlanner OAuth approval during connection.

If official auto-fill parameters for connector name and endpoint are not supported, XPlanner does not use undocumented URL parameters.

Codex CLI

Connect with Codex CLI

If you work from the terminal, you can add the XPlanner MCP server with Codex CLI.

Codex CLI must be installed and signed in.
Copy the command from the MCP drawer.
Run codex mcp add xplanner --url https://mcp.xplanner.co/mcp in your terminal.
If Codex asks for OAuth approval, complete the browser flow.

Claude Code CLI

Connect with Claude Code CLI

If you use Claude Code CLI, you can add the XPlanner MCP server from the terminal.

Claude Code CLI must be installed and signed in.
Copy the command from the MCP drawer.
Run claude mcp add --transport http xplanner https://mcp.xplanner.co/mcp in your terminal.
If Claude asks for OAuth approval, complete the connection flow.

Advanced Setup

When is manual config needed?

CLI commands are enough for most users. Manual config should only be used for custom setups or project-level MCP settings.

~/.codex/config.toml is the local Codex user configuration.
A project-level .codex/config.toml only stores settings for that project workspace.
With manual config, the server name should be xplanner and the endpoint should be https://mcp.xplanner.co/mcp.
The CLI method is the default recommendation because it creates the same configuration with less risk of mistakes.

Manual configuration is not required for regular users; that is why the MCP drawer shows a ready CLI command.

Troubleshooting

What should I check if the connection does not work?

The MCP connection is established between the client, OAuth, and your XPlanner account. If something goes wrong, verify the basic connection details first.

Check that the endpoint value is https://mcp.xplanner.co/mcp.
Make sure you are signed in to your XPlanner account.
If the OAuth approval window does not open, check your browser popup blocker.
If you use CLI, make sure the client is up to date.

How will the guide be updated?

When a new user flow occurs, this section is added as a new page to the same docs structure.

When the display language changes, the actual button and title names are checked again with Playwright smoke.

API-related flows are cross-linked to the relevant API v1 page.

Former

Social Sets

Fikirler