Your AI assistant, now publishes.
Hand your CrossPoster workspace to Claude Desktop, Cursor, or ChatGPT. They get a toolbelt — drafts, publishing, audits, personas, autonomous scheduling. You get one OAuth consent screen and zero copy-paste between tabs.
CrossPoster speaks Model Context Protocol (MCP) — the open standard every modern AI assistant supports.
Add CrossPoster to your assistant
One click for Cursor, or paste the server URL into any client's connector settings. OAuth runs the first time you connect — no keys.
What you can do
Three concrete examples. Same OAuth-scoped access for all three.
Schedule a LinkedIn post for tomorrow morning
Draft a LinkedIn post about our Q3 launch — focus on the new agent features — and schedule it for tomorrow at 9am London time.
Creates a draft, generates a caption tuned for LinkedIn voice, suggests publish time, schedules. Tools: create_draft → generate_caption → suggest_publish_time → schedule_post.
Generate a week of Instagram content from a single brief
Plan 5 Instagram posts for next week. Theme is 'behind the scenes at a startup'. Generate the images too. I'll review before anything ships.
Creates a calendar, generates captions + images per day, presents each draft for review. Nothing publishes until you explicitly approve. Tools: create_content_calendar → generate_image (×5).
Switch personas mid-conversation
Switch to my 'Founder thought leadership' persona, then audit my latest LinkedIn draft and tell me if it actually sounds like a founder, not like a marketer.
Switches active persona for the session, then runs a content audit scoring the draft across 7 dimensions. Tools: switch_persona → run_content_audit.
Claude Desktop, Claude.ai & ChatGPT
These connect through the app's own UI — no config file. Open Settings → Connectors → Add custom connector, and paste the server URL:
https://mcp.crossposter.tech/mcp
OAuth runs on first connect — sign in and approve the scopes. ChatGPT connectors need a paid plan (Plus, Pro, Business, or Enterprise).
Cursor
Use the Add to Cursor button above, or add this to ~/.cursor/mcp.json. Cursor discovers OAuth from the URL — no client ID or keys to paste.
{
"mcpServers": {
"crossposter": {
"url": "https://mcp.crossposter.tech/mcp"
}
}
}Available scopes
Each scope grants a fixed capability cluster. You approve them on the consent screen when you connect; revoke individual tokens anytime in Integrations.
| Scope | What it grants |
|---|---|
| tools.read | Read drafts, posts, platforms; recall memory. |
| tools.drafts.write | Create, edit, transform drafts. |
| tools.content.generate | Generate new content, improve captions. |
| tools.media.generate | Generate AI images, videos, edits. |
| tools.publish | Publish or schedule posts. |
| tools.audit | Score content; run compliance checks. |
| tools.memory.write | Save / delete / clear memories. |
| tools.workflows | Create calendars, request team approval. |
| tools.persona | Switch + configure personas. |
| tools.autonomous | Configure autonomous publishing thresholds. |
How OAuth works
- You add CrossPoster to your AI client (the buttons above, or paste the URL into its connector settings).
- On first connect, the client opens a browser tab to app.crossposter.tech.
- You sign in (if you weren't already) and approve the scopes the client requested.
- The client receives an access token via PKCE + RFC 7591 dynamic registration. No keys to manage.
- You revoke or rotate any time at
/settings/integrations.
Legacy cp_live_* keys keep working — no breaking changes. Add them to your MCP client as x-api-key headers. OAuth is the recommended new path; API keys remain available.