Connect PostKing to Claude, ChatGPT and Cursor
Add the PostKing connector at https://mcp.postking.app/mcp and sign in with OAuth. No API key, no install.
PostKing runs a hosted MCP server. Add it to your assistant as a remote connector, sign in to PostKing in the browser window that opens, and your assistant can work on your brands.
| Server URL | https://mcp.postking.app/mcp |
| Transport | Streamable HTTP |
| Sign-in | OAuth (a PostKing sign-in window opens in your browser) |
| API key needed | No |
| Local install (npx, npm) needed | No |
Vera, the assistant inside PostKing, is not the MCP server. Vera lives in the dashboard. The connector lets a different assistant (Claude, ChatGPT, Cursor) use your PostKing account.
Claude.ai and Claude Desktop
Both use the same custom connector.
- Open Settings, then Connectors.
- Choose Add custom connector.
- Name it
PostKingand pastehttps://mcp.postking.app/mcp. - Save, then choose Connect. Sign in to PostKing and approve access.
- In a chat, enable the PostKing connector from the tools menu.
Menu names can differ slightly by plan and app version. Custom connectors are not available on every Claude plan; if you do not see the option, check your plan or ask your workspace admin.
Claude Code
Run this once in your terminal:
claude mcp add --transport http postking https://mcp.postking.app/mcpThen start claude, run /mcp, select postking and choose Authenticate. A browser window opens for the PostKing sign-in.
Optional: install the PostKing skills so Claude Code knows the right tool order for posts, blogs, SEO and landing pages.
claude plugin marketplace add bitsandtea/postking-skillsclaude plugin install postkingChatGPT
- Open Settings, then Connectors. If custom connectors are hidden, enable developer mode under the advanced settings first.
- Create a connector. Name it
PostKing, set the server URL tohttps://mcp.postking.app/mcp, and choose OAuth for authentication. - Connect, sign in to PostKing and approve.
- In a new chat, add the PostKing connector from the tools menu.
Where this lives in ChatGPT depends on your plan and workspace settings; admins may need to allow custom connectors.
Cursor
Add PostKing to your MCP config (~/.cursor/mcp.json for all projects, or .cursor/mcp.json in one project):
{
"mcpServers": {
"postking": {
"url": "https://mcp.postking.app/mcp"
}
}
}Open Cursor Settings, then MCP, and choose Connect next to postking. Sign in to PostKing in the browser window.
Other clients
Any client that supports remote MCP servers over Streamable HTTP with OAuth works. Give it the URL https://mcp.postking.app/mcp and let it run the sign-in. The server advertises its OAuth details through standard discovery, so clients that register themselves need nothing else.
Clients that only support local (stdio) servers cannot use this URL directly.
First prompts to try
Start with one brand, then work outward.
- "List my PostKing brands, then make
<brand>the active one." - "Show my credit balance."
- "Onboard https://yoursite.com as a new brand."
- "Which social accounts are connected for this brand?"
- "Write 3 LinkedIn post options about
<topic>. Don't schedule anything yet." - "Schedule the second option for Thursday at 9am."
- "Show what's on my calendar for the next 14 days."
- "Turn this article into posts for X and LinkedIn:
<url>." - "Suggest blog topics for my brand and start keyword research from these seeds:
<3-10 topics>." - "Generate a landing page for
<offer>, then show me the draft."
Generation uses credits. Ask for your balance first if you are unsure. See Billing and credits.
Troubleshooting
See MCP troubleshooting for sign-in loops, the wrong brand being used, and re-authorizing.