Find your workspace
List the Posty workspaces I can access and the channels connected to each one.Your AI.
Your voice.
Your next post.
Bring your social workspace into the AI tools you already use. Turn ideas into drafts, move reviews forward, and schedule what’s next.
Connect your assistantSign in with Posty. No API key to manage.

Launch workspace
LinkedIn · Draft
Small improvements. A better everyday workflow.
Here’s what we’ve been building, and what it means for your next project.
Your workspace. Your existing permissions.
Choose your assistant. Connect Posty.
Pick a workspace and start creating.
https://api.posty.social/mcpOne command in the Codex CLI adds Posty to the CLI, the IDE extension and the Codex app at once.
Official Codex guideThe same permissions as Posty
Your assistant can only access workspaces you belong to and perform actions you’re allowed to take.
Run this in any terminal. Codex writes the server to its configuration, which the CLI, the IDE extension and the Codex app share, so you only add it once.
codex mcp add posty --url https://api.posty.social/mcpPosty opens in your browser. Sign in, choose the workspaces this connection may reach and approve access. No API key is created or pasted anywhere. If setup did not already prompt you, start the sign-in yourself.
codex mcp login postyOpen a new Codex session and ask it to list your Posty workspaces. Name the one you want in each request. Codex shows connected servers and their tools when you run its MCP command inside a session.
/mcpOne command adds Posty for all your projects; share it with a team through a committed .mcp.json.
Full Claude Code guide, with FAQ
Official Claude Code guideThe same permissions as Posty
Your assistant can only access workspaces you belong to and perform actions you’re allowed to take.
Run this in any terminal. The user scope makes Posty available in every project; drop the scope flag to keep it to the current project, or use the project scope to write a .mcp.json your team can commit.
claude mcp add --transport http --scope user posty https://api.posty.social/mcpStart Claude Code, run its MCP command, select Posty and follow the prompts. Posty opens in your browser. Sign in, choose the workspaces this connection may reach and approve access. No API key is created or pasted anywhere. Tokens are stored securely and refreshed for you.
/mcpBack in Claude Code, ask it to list your Posty workspaces, then name the one you want in each request. Approve tool calls when prompted. The VS Code and JetBrains extensions use the same configuration, so the server is there too.
A custom connector in Claude’s settings, managed through your Claude account on the web and desktop.
Official Claude guideThe same permissions as Posty
Your assistant can only access workspaces you belong to and perform actions you’re allowed to take.
In Claude, open Customize, then Connectors, choose Add and then Add custom connector. Name it Posty and paste this remote MCP server URL. Claude detects the sign-in settings itself.
https://api.posty.social/mcpChoose Connect on the new Posty connector. Posty opens in your browser. Sign in, choose the workspaces this connection may reach and approve access. No API key is created or pasted anywhere. On a Team or Enterprise plan an Owner adds the connector under Organization settings first, then each member connects.
In a chat, open the plus menu, choose Connectors and switch Posty on, then ask Claude to list your workspaces. Claude asks before each tool call unless you allow a tool always.
A short mcp.json entry, global or per project, makes Posty available to Cursor’s agent.
Official Cursor guideThe same permissions as Posty
Your assistant can only access workspaces you belong to and perform actions you’re allowed to take.
Add this to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json inside one repository. If the file already has other servers, merge the posty entry into the existing mcpServers object.
{
"mcpServers": {
"posty": {
"url": "https://api.posty.social/mcp"
}
}
}Open Cursor’s MCP settings, find Posty and connect. Posty opens in your browser. Sign in, choose the workspaces this connection may reach and approve access. No API key is created or pasted anywhere.
Open the agent, make sure the Posty tools are enabled and ask it to list your workspaces. Name the workspace you want in each request. Cursor asks before running a tool by default.
OpenCode’s guided add command registers Posty as a remote server without hand-editing configuration.
Official OpenCode guideThe same permissions as Posty
Your assistant can only access workspaces you belong to and perform actions you’re allowed to take.
Run the guided add command. Name the server posty, choose Remote and enter https://api.posty.social/mcp as the URL. OpenCode writes a remote entry with OAuth detection to your configuration.
opencode mcp addPosty opens in your browser. Sign in, choose the workspaces this connection may reach and approve access. No API key is created or pasted anywhere. OpenCode also starts the sign-in on its own the first time a tool answers that it needs one.
opencode mcp auth postyCheck the connection with the list command, then ask OpenCode to list your Posty workspaces and name the one you want in each request.
opencode mcp listA .vscode/mcp.json entry gives Copilot agent chat the Posty tools, per workspace or for your whole profile.
Official VS Code guideThe same permissions as Posty
Your assistant can only access workspaces you belong to and perform actions you’re allowed to take.
Add this to .vscode/mcp.json in your workspace so the whole team gets it, or run MCP: Add Server from the Command Palette and choose HTTP to add it to your profile. Merge the posty entry if the file already has servers.
{
"servers": {
"posty": {
"type": "http",
"url": "https://api.posty.social/mcp"
}
}
}Run MCP: List Servers, choose Posty and start it. Review the trust prompt. Posty opens in your browser. Sign in, choose the workspaces this connection may reach and approve access. No API key is created or pasted anywhere.
Open Copilot chat in agent mode, pick the Posty tools in the tools picker and ask it to list your workspaces. Name the one you want in each request. If nothing starts, your organisation may restrict MCP servers.
Using another client? Add the server URL as a remote HTTP MCP server with OAuth authentication. Your client needs remote MCP and OAuth support.
Every tool mirrors one operation of the public API, so anything a script can do, your assistant can do, within your role. The server publishes its full tool catalog with every schema.
create_postupdate_post_contentbulk_schedule_postsact_on_postlist_post_review_requestsget_post_historycreate_media_uploadreplace_post_content_mediaset_media_alt_textcreate_campaignadd_post_to_campaignget_campaign_resultsget_analytics_overviewget_analytics_detailget_post_native_metricslist_inbox_conversationslist_post_commentscreate_post_commentA few things to try once you’re connected. Replace “Launch” with your workspace name and bring your own ideas.
List the Posty workspaces I can access and the channels connected to each one.In my Launch workspace, draft a LinkedIn post from these release notes. Keep it as a draft for me to review.Show me the posts scheduled for next week in my Launch workspace, grouped by channel.Posty checks workspace membership and permissions on every call. Drafts, approvals and scheduling follow the same rules as the app, and a token never freezes a permission you have since lost.
You can work across any workspace you have access to. Tell your assistant which one to use, review its drafts, and publish when you’re ready. See the roles and visibility matrix for what each role can do.