PostKing MCP server
Commit Nov 12, 2026Manage brands, generate social media posts, schedule content, and publish blog articles through an AI-powered content platform.
Also known as bitsandtea/postking-mcp
- Stars
- 1
- Tools
- 220
- Downloads, 30 days
- —
- Latest version
- 1.1.7
- Last commit
- Nov 12, 2026
- License
- —
What is PostKing MCP?
PostKing manages brands, generate social media posts, schedule content, and publish blog articles through an AI-powered content platform. It exposes 220 tools, such as login_start, login_complete, logout.
Summary generated from the project's README
About PostKing MCP server
PostKing MCP connects AI clients like Claude Desktop, Cursor, or Claude Code to the PostKing content platform. This server allows users to manage brands, social media, and blog publishing through a conversational interface. It provides full parity with the postking-cli, offering 291 tools organized into 33 modules for comprehensive content operations.
Users can manage their entire workflow by generating social media posts, scheduling content, or repurposing existing URLs into new formats. The server supports complex SEO and GEO research workflows, enabling the creation of keyword clusters and content roadmaps. It also handles blog management, including writing articles and publishing them to platforms like WordPress, Medium, or Substack.
Setup is handled via a device login flow rather than manual API key entry. By telling the client to login, users follow a URL to approve access, which then saves a permanent token locally. The server works via local stdio or a remote HTTP transport at mcp.postking.app.
What you can do with it
- 1Execute SEO research workflowsStart an SEO research project by providing seed keywords to generate clusters and a content roadmap.
Written from the project's README. Every use case is checked against a quote from it.
How to install PostKing MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall PostKing MCP in Claude Code
$ claude mcp add postking-mcp -- npx -y postking-mcpInstall PostKing MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"postking-mcp": {
"command": "npx",
"args": [
"-y",
"postking-mcp"
]
}
}
}Install PostKing MCP in VS Code
.vscode/mcp.json
{
"servers": {
"postking-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"postking-mcp"
]
}
}
}Install PostKing MCP in VS Code CLI
$ code --add-mcp '{"name":"postking-mcp","type":"stdio","command":"npx","args":["-y","postking-mcp"]}'Install PostKing MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"postking-mcp": {
"command": "npx",
"args": [
"-y",
"postking-mcp"
]
}
}
}Install PostKing MCP in Codex
$ codex mcp add postking-mcp -- npx -y postking-mcpInstall PostKing MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.postking-mcp] command = "npx" args = ["-y", "postking-mcp"]
Install PostKing MCP in Gemini CLI
$ gemini mcp add -s user postking-mcp npx -- -y postking-mcpInstall PostKing MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"postking-mcp": {
"command": "npx",
"args": [
"-y",
"postking-mcp"
]
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for postking-mcp 1.1.7 in an isolated container with no network and no keys. It answered and listed 220 tools.
PostKing MCP tools 220
Read from the server with tools/listlogin_startStart the PostKing login flow. Returns a URL and short code for the user to visit in their browser. IMPORTANT: Immediately after this tool returns, show the URL + code to the user and then call `login_complete` — it will wait (polling in the background) until the user approves the request in their browser, so there is no need to ask the user to tell you when they are done.
login_completeWait for the user to approve the PostKing login code in their browser and then save the token. Polls automatically; call this immediately after `login_start`.
logoutClear locally stored PostKing credentials.
whoamiReturn the profile of the currently authenticated PostKing user (email, plan, credit balance, token source).
list_brandsList all brands on your PostKing account. Returns id+name+website by default (short). Use detail='medium' for description, 'full' for all raw fields. To zoom into one brand call get_brand_info with detail='full'.
set_active_brandSet the active brand for this session. All subsequent tools will use this brand by default.
get_brand_infoGet a brand's profile. Returns core identity fields plus slim summaries: themes as [{id,title}], voiceProfiles as [{id,name,isActive,optimizedMedium}], blogAuthors as [{id,firstName,lastName}], and postCount/memberCount as numbers. Use list_themes, list_voices, list_blog_authors, list_posts, or get_brand_members for full detail on each.
create_brandSTEP 1 of brand onboarding (manual path — no website crawl). Creates a new brand from user-supplied name/description, sets it as active, then RETURNS a `nextStep` payload telling you to ask the user which platforms they publish on. After the user answers, call `set_brand_mediums` with their picks. Ask the user for a description if they did not provide one — onboarding will fail without it.
onboard_brandSTEP 1 of brand onboarding (website path). Crawls the site in the background and kicks off audience analysis + 10 themes. Sets the new brand as active and RETURNS a `nextStep` payload. IMMEDIATELY after this returns, ask the user which social platforms they publish on, then call `set_brand_mediums`. Do not call `get_onboarding_status` until mediums are set.
set_brand_mediumsSTEP 2 of brand onboarding. Saves the list of platforms the brand publishes on. Call this immediately after `create_brand` or `onboard_brand` and the user has picked platforms. After this, call `get_onboarding_status` every ~15 seconds until it reports `done`.
get_brand_mediumsRead which publishing platforms (mediums) a brand posts to. Read-only counterpart to set_brand_mediums. NOTE: Reddit is NOT a medium — Reddit is a separate repurpose module; use the reddit_* tools or dashboard_link section 'reddit'.
get_brand_membersList all active members of a brand with their role and user info (id, name, email).
Show all 220 toolsShow fewer tools
get_onboarding_statusSTEP 3 of brand onboarding. Polls background analysis + theme generation. detail='short' returns status only; detail='medium' (default) adds audienceSummary+themeCount; detail='full' returns raw data. Poll every ~15s. When done, surface the audience review + themes to the user.
list_themesList all content themes for the active brand with their IDs. detail='short' (default) returns id+title; detail='medium' adds content preview; detail='full' returns raw content.
edit_themeEdit an existing content theme's title or content instructions.
delete_themeDelete a content theme from the active brand.
generate_themesGenerate new content themes using AI. Polls until complete. Deducts credits.
get_social_media_rulesRead a brand's per-platform social media content rules (the same rules editable in dashboard Settings → Social media rules). Covers content/structure/engagement/visual-strategy guidance plus secrets, guidelines, content types, things to avoid, and core principles. Call this BEFORE set_social_media_rules so you only change the fields you intend to.
set_social_media_rulesUpdate a brand's social media content rules for ONE platform. By default this MERGES your provided fields into the existing rules (send only what you want to change — other fields are preserved; arrays you provide replace the old array). Set replace=true to overwrite the entire platform ruleset. Valid platforms: linkedin, x/twitter, facebook, instagram, threads, general. Tip: call get_social_media_rules first to see current values.
generate_postGenerate AI content for a platform. Polls until complete. Deducts 10 credits per variation. To control what the post is about, pass `theme` with a free-text brief (any topic/angle/facts/tone). If you omit `theme`, the topic is RANDOM — so always pass it when the user wants specific content. When variations > 1, ALL variations are returned under a SINGLE postId in the `variations` array — it does NOT create one post per variation. `content` is variation 1 (the primary, already saved on the post). Never call generate_post again to 'get the other variations' — they're all in the response. `originalContent` (if seen elsewhere) is the pre-voice-rewrite draft, not a separate variation. After generating, use create_post to save a chosen variation, then approve_post to schedule it. To repurpose: call repurpose_content first, then create_post with the result, then approve_post. Generation can take 1-5 minutes (longer with multiple variations or voice rewrite); this tool waits for completion. If it ever returns status 'still_generating', DO NOT write the post yourself — poll get_post with the returned postId until operationStatus is 'completed', then use that content. After generation, brand visual options (quote/card templates, brand images, stock photos) are prepared but NOT attached — share viewInBrowser for the visual picker, or call pick_post_visual to attach one. Do not attach a visual unless the user chooses it. The response includes editInVisualEditor: a direct URL to edit the post in the visual editor.
generate_bulk_postsGenerate and schedule multiple posts across a date range in the background.
create_postSave a post draft with custom content to one or more platforms. Supported platforms: x, linkedin, instagram, threads, facebook. After creating, call approve_post with a future ISO 8601 datetime to schedule it. To check which platforms are connected first, call check_social_accounts. Each created post includes editInVisualEditor: a direct URL to edit it in the visual editor.
list_postsList recent posts and drafts. Filter by status or platform. Use status='created' to find unscheduled drafts. Returns id+status+scheduledAt by default; use detail='medium' or 'full' for more fields. For a single post use get_post.
get_postView the full content and status of a single post. Use detail='short'|'medium'|'full' to control verbosity (default full). Multi-variation posts expose a `variations` array (all variations live on one postId). Output shows the final voice-rewritten content by default; pass includeOriginal=true to also see the pre-rewrite draft. Includes editInVisualEditor: a direct URL to edit the post in the visual editor.
approve_postApprove and schedule a draft post. Requires a future datetime. The scheduledAt must be an ISO 8601 UTC datetime, e.g. 2026-03-11T09:00:00Z. After approving, the post status becomes 'scheduled'.
reschedule_postMove a scheduled post to a new time. Pass a future ISO 8601 UTC datetime.
schedule_postSchedule a draft or approved post for a specific time. Equivalent to approve_post but named to match 'pking posts schedule'. Pass a future ISO 8601 UTC datetime. After scheduling the post status becomes 'scheduled'.
cancel_postCancel a scheduled or approved post, reverting it to draft status without deleting it. Use delete_post to remove it entirely.
delete_postCancel and delete a post regardless of its current status (draft, scheduled, or posted).
get_calendarView upcoming scheduled posts sorted by date. Returns id+status+scheduledAt by default; use detail='medium' or 'full' for more fields. For a single post use get_post.
repurpose_contentTurn a URL, text, blog post, or existing PostKing post into new content for social media or blogs. IMPORTANT: When the source is a URL, pass it directly to this tool via sourceUrl — do NOT fetch or crawl the URL yourself first. PostKing handles all crawling internally. Source types: url | text | blog | social_post. Target types: social (LinkedIn, X, etc.) | blog | text. Supports detail param: short=ids only, medium=key fields (default), full=raw response.
generate_textGenerate or rewrite general-purpose, email-style/formal text — follow-up emails, cover letters, outreach messages, formal notes, etc. Polls until complete. This is NOT for social media posts — use generate_post for those. This is also NOT for a simple voice-only rewrite of existing text with no other options — for that, use rewrite_with_voice or rewrite_text instead. Reach for generate_text when you need mode selection (generate vs rewrite), a stated purpose, a target length, or when there's no source text at all (mode='generate'). mode='generate' writes new text from a `prompt` (what to write, e.g. 'a follow-up email after a sales call, polite but direct'). mode='rewrite' rewrites existing `sourceText` into a new form/tone. `purpose` is optional free text describing the goal, e.g. 'win-back email' or 'job application cover letter'. `length` can be short | medium | long, or a specific target word count (20-5000). Supports detail param: short=status+wordCount only, medium=truncated content (500 chars)+wordCount (default), full=raw result including content, aiDetectionScore, burstinessScore, promptLogId, wordCount.
list_voicesList all available voice profiles with their IDs. Lists default short; pass detail=medium/full for more fields.
rewrite_with_voiceRewrite text using a specific voice profile.
rewrite_textRewrite text using a voice profile or general writing rules.
humanize_textApply LLM rewrite and BERT replacements to reduce AI detection signals in text.
check_ai_contentCheck whether text is likely AI-generated. Returns a score and analysis.
check_social_accountsList all connected and disconnected social accounts for the active brand. Lists default short; pass detail=medium/full for more fields. Run before posting to confirm platform availability.
generate_connect_linkGenerate a secure browser link to connect a social media account. Share this URL with the user to complete OAuth.
disconnect_social_accountDisconnect a social account by its account ID.
list_domainsList all custom domains for the active brand. Lists default short; pass detail=medium/full for more fields including SSL status, verification, and connected blogs or landing pages.
add_domainAdd a new custom domain to the active brand. After adding, call verify_domain to check DNS and activate it.
verify_domainCheck DNS verification for a domain. Returns whether it's pointing to PostKing servers and what A record is needed if not.
delete_domainRemove a custom domain. Connected blogs and landing pages are unlinked but not deleted.
connect_domain_to_publicationConnect a verified domain to a blog publication so articles are served from that domain.
get_creditsCheck your current PostKing credit balance and free-tier status.
healthCheck PostKing API health and local auth state. No authentication required — safe to call first thing in a session to see whether you're logged in and what to do next.
list_blogsLIST tool. Even detail='full' OMITS article bodies (kept bounded) — to read an article's content, call get_blog_article. The number of rows is controlled by `limit` (default 50, max 200), NOT by `detail`; for a 'full list' of titles, raise `limit` and keep detail='short'.
create_publicationCreate a new blog publication (the container that articles live under). Returns a publicationId needed for generate_blog_post.
update_publicationUpdate an existing blog publication's metadata — title, description, domain/routing config, or layout. Only the fields you pass are changed (partial update). Distinct from create_publication (which creates a new one). publicationId comes from list_publications or list_blogs.
generate_blog_postGenerate a full AI blog article. Requires a publicationId (from list_blogs or create_publication). Pass a voiceProfileId to write in a specific person's style (IDs from list_voices). Returns an articleId + operationId; generation is async — poll get_blog_status until completed, then get_blog_article. Use update_blog_article to edit, or publish_blog_article to push to external platforms. To make it live on your PostKing blog, call update_blog_article with status: 'published'.
get_blog_articleFetch a blog article by ID. detail='short' returns id/title/slug/status; detail='medium' adds excerpt+wordCount+previewUrl+editUrl; detail='full' (default) returns the COMPLETE content plus previewUrl (GUI preview link) and editUrl (dashboard editor link). Pass maxContentChars only if you need to bound the body size; omit it to get the whole article.
update_blog_articleEdit a blog article — title, content, excerpt, SEO fields, status, author, or category. Set status='published' to make it live on your PostKing blog.
schedule_blog_articleSchedule an existing blog article to auto-publish at a future date/time. scheduledAt must be a future ISO 8601 datetime. When the time arrives, the article publishes to the PostKing blog and auto-pushes to any connected external platforms flagged autoPublish. To publish immediately instead, use update_blog_article with status='published'.
delete_blog_articlePermanently delete a blog article.
list_blog_authorsList all blog authors for the active brand. Returns id+name by default (short); use detail='medium' for email/social links. Author IDs can be passed to generate_blog_post or update_blog_article.
list_blog_categoriesList all categories for a blog publication. Returns id+name+slug by default (short); use detail='medium' for description+articleCount.
create_blog_categoryCreate a new category in a blog publication.
list_publishing_connectionsList external publishing connections for a blog publication (WordPress, Medium, Substack, etc.).
publish_blog_articlePush a blog article to connected external platforms (WordPress, Medium, Substack, etc.). Get connection IDs from list_publishing_connections.
import_blog_articlesImport articles from an external blog, RSS feed, or Blogger URL into a PostKing publication as drafts. Returns id+title+slug by default (short); use detail='medium' for wordCount. Inspect individual articles with get_blog_article.
get_blog_statusPoll the async generation status of a blog article. Use the articleId returned by generate_blog_post. Status: pending | running | completed | failed.
create_blog_authorCreate a new author for blog articles. Returns an authorId that can be used in generate_blog_post and update_blog_article.
list_publicationsList all blog publications (the containers that blog articles live under). detail='short' returns id+name; detail='full' returns raw rows. Distinct from list_publishing_connections which lists external platforms like WordPress.
get_seo_roadmapView the SEO / GEO content roadmap — suggested blog topics, keywords, and completion status. detail='short' returns stats only; detail='medium' adds slim item list (id+title+status+keyword); detail='full' (default) returns raw response.
seo_add_seedsStep 1 of the SEO / GEO flow. Add 3–10 seed keywords that describe what the brand wants to rank for. After this, call seo_generate_keywords to expand them into the full keyword universe.
seo_generate_keywordsStep 2 of the SEO / GEO flow. Async — expands seed keywords into the full keyword universe. Typically takes ~1–3 min. Uses credits. Returns `{operationId, status}` — Poll `get_job` with the operationId until `state` is `completed` (or `failed`/`partially_failed`/`cancelled` on error). The server picks the expansion size automatically; the only thing the agent can tweak is `autoScore` (defaults to true server-side — set false to skip volume/difficulty scoring). After completion, call seo_categorize.
seo_list_keywordsList generated keywords for the brand. Useful for auditing between steps. Returns short detail by default: {id, keyword, intent} per keyword. Use detail="medium" for the full compact summary (priority, searchVolume, difficulty, excludedFromClustering, userTags) or detail="full" for raw keyword objects.
seo_edit_keywordEdit a single SeoScoredKeyword. Housekeeping op — not part of the main flow. At least one of `intent`, `userTags`, `priority`, or `excludedFromClustering` must be supplied. Use to override the auto-detected intent label, attach user tags, manually nudge priority (0..1), or exclude a noisy keyword from clustering. Example: {"keywordId":"kw_123","intent":"commercial","userTags":["enterprise"]}.
seo_delete_keywordSoft-delete a single SeoScoredKeyword (sets deletedAt; the row stays in the DB but is filtered out of all queries). Housekeeping op — not part of the main flow. Pass `confirm: true` to proceed. Use for obvious junk keywords the auto-pipeline missed. Prefer seo_edit_keyword with excludedFromClustering=true when you only want to hold a keyword out of the next clustering pass.
seo_categorizeStep 3 of the SEO / GEO flow. Tag keywords by search intent and/or user tags. Pass `updates`: an array of `{keywordId, intent?, userTags?}` (intent ∈ informational | commercial | navigational | transactional). Example: {"updates":[{"keywordId":"kw_123","intent":"commercial"}]}. After this, call seo_generate_clusters.
seo_generate_clustersStep 4 of the SEO / GEO flow — async cluster-generation step. Groups related keywords into topic clusters that become candidate pillar topics. Typically takes ~1–2 min. Returns `{operationId, status}` — Poll `get_job` with the operationId until `state` is `completed` (or `failed`/`partially_failed`/`cancelled` on error). After completion, call seo_list_clusters to pick a target, then seo_generate_roadmap.
seo_list_clustersStep 5. List clusters so the agent can pick one (or several) to approve before brief and roadmap generation. Returns short detail by default: {id, name, status} per cluster. Use detail="medium" for the full compact summary (pillarKeyword, briefGenerationStatus, briefCount, keywordCount, topKeywords, firstBriefId, description) or detail="full" for raw cluster objects. Full keyword detail (keywordsMeta, contentMix, briefAssignments) is intentionally omitted at short/medium to keep context small — use cluster IDs with approve/reject tools directly.
seo_bulk_approve_clustersStep 5b — bulk-approve N clusters in one call. Recommended path when an agent wants to move multiple clusters forward. Approving a cluster fires an async seo_brief_generate Operation per cluster; brief generation only runs on approved clusters. Typically takes ~2–5 min per cluster. Response includes `operations: [{ clusterId, operationId }]` and `operationIds: string[]` — Poll `get_job` with the operationId until `state` is `completed` (or `failed`/`partially_failed`/`cancelled` on error).
seo_approve_clusterApprove a single cluster. Gates brief generation — only approved clusters get briefs drafted. Position in flow: after seo_generate_clusters + seo_list_clusters, before seo_generate_roadmap / brief review. Typically takes ~2–5 min per cluster. Returns `{ cluster, operationId }` — the operationId is for the async brief-generation job kicked off by approval. Poll `get_job` with the operationId until `state` is `completed` (or `failed`/`partially_failed`/`cancelled` on error).
seo_reject_clusterReject a single cluster — marks it rejected and detaches its scored keywords. Use when a generated cluster isn't relevant.
seo_bulk_reject_clustersBulk-reject N clusters in one call. Symmetric to seo_bulk_approve_clusters.
seo_unapprove_clusterRevert an approved cluster back to pending_review. Fails if briefs have already been generated for this cluster (cannot be reverted once briefs exist).
seo_restore_clusterRestore a rejected cluster back to pending_review so it can be approved again.
seo_generate_roadmapStep 6. Turn one or more clusters into a prioritized content roadmap of blog articles to write. Pass `clusterId` (single) or `clusterIds` (array of cluster IDs from seo_list_clusters) — omit both to roadmap all clusters. After this, call seo_write_article.
seo_list_roadmapList roadmap items (blog topics queued for writing). Returns short detail by default: {id, title, status} per item. Use detail="medium" for the compact summary (priority, primaryKeywords, clusterId) or detail="full" for raw objects. Call seo_roadmap_get with detail="full" for a single item's complete detail.
seo_list_briefsReturns ALL briefs across EVERY status by default — do NOT add a status filter unless the user explicitly asks. `statusBreakdown` gives the per-status counts (match these to the dashboard's brief count). NOTE: briefs whose generation is still in-flight may not appear here yet — check `list_operations` / `get_job` for in-progress generation. Returns short detail by default: {id, type, status, title} per brief. Use detail="medium" for compact summary (clusterId, clusterName, briefSummary, sidePageUrl, generationError, blogArticleId, generatedAt, approvedAt) or detail="full" for raw briefs including briefData outline. To inspect a single brief's full outline, call seo_get_brief with detail="full". Filters: status (CSV — e.g. 'pending_review,approved'), type (CSV — e.g. 'blog,comparison,landing'), clusterId, roadmapItemId, q (cluster-name fuzzy match), limit (default 50, max 200), cursor. Response shape: { count, total, nextCursor, statusBreakdown, detail, briefs: [...] }.
seo_get_briefFetch a single SeoBrief by id, including its briefData outline, status, roadmap item, and cluster. Returns full detail by default (complete brief incl briefData). Use detail="medium" for {id, type, status, title, clusterName, briefSummary, sidePageUrl} or detail="short" for {id, type, status}. Use to inspect a brief before refining it with seo_edit_brief or approving it with seo_approve_briefs.
seo_edit_briefEdit an SeoBrief before approval. The inner route does NOT accept free-text 'instructions' — refinement is structured. Pass `briefData` (the full replacement JSON for the brief outline — H2s, FAQs, keyword targets, etc.) and/or `status` ('approved' | 'rejected'). Approving via this tool fires L4 article/comparison generation immediately and returns { brief, operationId } — prefer seo_approve_briefs for the canonical approval step. Typical refinement loop: seo_get_brief → mutate briefData locally → seo_edit_brief with the new briefData (status omitted) → seo_approve_briefs.
seo_approve_briefsApproves one or more SeoBriefs and AUTO-fires L4 article/comparison generation immediately — do NOT call seo_write_article after this. Typically takes ~3–8 min per article. After approval, poll each returned operationId with get_job until state is `completed` (or `failed`/`partially_failed`/`cancelled` on error). A brief in status `writing` means generation is already in progress — poll the existing operation, do not re-submit. Body: briefIds (array, max 200). Response: { approved, failed: [{briefId, reason}], operationIds, operations: [{briefId, operationId, type}] }.
seo_list_resultsList the 'Generated Results' (blog articles + side pages + comparisons) the SEO/GEO pipeline has produced — mirrors the dashboard Results tab. Includes BOTH draft and published items. Use kind to filter. This is the canonical 'what content has been generated' list — prefer it over reconstructing results from briefs.
seo_regenerate_briefRe-runs L3 brief generation for a single brief (scoped to its cluster). Typically takes ~2–5 min. Async — returns `{operationId, status}`. Poll `get_job` with the operationId until `state` is `completed` (or `failed`/`partially_failed`/`cancelled` on error), then re-fetch with seo_get_brief to see the refreshed briefData. Use when the existing brief's outline is unusable and a structured seo_edit_brief won't recover it.
seo_write_articleALTERNATIVE write path — only call this when a brief was NOT approved via seo_approve_briefs (which already auto-generates). If the brief status is `writing`, generation is already in progress — poll the existing operationId with get_job until state is `completed` rather than calling this again. Step 7 (manual path). Draft a full blog article for a roadmap item. Uses credits. Typically takes ~3–8 min per article. Precondition: the brief for this roadmap item must be in status `approved`. If the brief is still `drafted` or `pending_review`, review with `seo_list_briefs` / `seo_get_brief`, refine with `seo_edit_brief`, then approve with `seo_approve_briefs` (which will auto-generate). Returns an articleId that can be reviewed, edited, or published.
seo_gapIdentify content gaps — topics the brand's competitors cover but the brand doesn't. Returns short detail by default: {id?, topic?, keyword?} labels only per gap. Use detail="medium" for compact gaps (+ searchVolume, difficulty, competitorDomains) or detail="full" for the raw API response.
seo_competitorCompare the brand's keyword coverage against a competitor domain. Returns short detail by default: bucket totals only {overlapping: {total}, brandUnique: {total}, competitorOnly: {total}}. Use detail="medium" for capped keyword lists (up to 50 per bucket) or detail="full" for the raw API response.
seo_roadmap_getView a single roadmap item by ID. Returns full detail by default (raw object). Use detail="medium" for {id, title, status, primaryKeywords, clusterId} or detail="short" for {id, title, status}.
seo_roadmap_editEdit a roadmap item — update its title, status (suggested|in_progress|completed|ignored), or priority.
seo_roadmap_deletePermanently delete a roadmap item. Pass confirm: true to proceed — this is irreversible.
seo_roadmap_statsProgress stats for the content roadmap (completed, in-progress, suggested counts).
seo_publish_articleStep 10. Publish or schedule a roadmap-generated article to a publication. Free-tier choke point — may return FREE_CAP_REACHED with a checkoutUrl.
seo_auto_assign_ctaOptional capstone step — runs AFTER blog articles are published. Auto-suggests a published side-page CTA for each blog article in the batch by matching the article's keywords (cluster + tags + title) against the brand's published side pages, then writes the result to BlogArticle.sidePageInfo (header + ctaText + ctaButtonText + ctaHref). Defaults are safe to re-run: skips blogs that already have a CTA (`overwriteExisting=false`) and skips Webflow-synced blogs (`skipWebflowSynced=true`) since CTA edits don't push back to Webflow. Synchronous — returns `{ updated, skipped, errors, total, results: [{blogId, status, sidePageId?, sidePageSlug?}] }` directly; no polling needed. Pass `blogIds: "all"` to process every blog for the brand, or a list of up to 50 blog IDs. Hard cap of 50 blogs per call. For brands with more uncovered blogs, batch your `blogIds` arrays in groups of 50. The matcher uses keywords today; reusing an existing CTA header/ctaText body as a matching signal is a planned enhancement.
seo_generate_side_pageGenerates a side page for a brand's landing page, optionally linked to an SEO cluster (`clusterId`). When linked, the side page surfaces in cluster-context queries and inherits the cluster's keyword targeting — strengthening topical authority that feeds GEO citation patterns. Two body modes: • freeform: pass `key` + `prompt` (+ optional `keywords`, `selectedSections`, `voiceProfileId`, `sidePageType`). • brief: pass `key` + `brief` (structured outline) + optional `briefId` and `roadmapItemId`. Typically takes ~2–5 min. Async — returns `{ success, operationId, operationRowId, pollUrl, sidePageId }`. Poll `get_job` with the operationId until `state` is `completed` (or `failed`/`partially_failed`/`cancelled` on error); comparison-type briefs run synchronously and return `sidePageId` directly. `slug` is the PARENT landing page slug under which the side page is created.
create_comparison_pageCreate a comparison / 'X vs Y' / 'best <category>' page for the brand WITHOUT going through the full SEO cluster → brief flow. One call kicks off generation, then this tool polls until the page is built and returns its slug(s) + link. `mode` controls the engine: 'research' crawls the named competitors + live SERP results before writing — slower (can take several minutes) but produces the strongest, best-grounded page; 'simple' skips all crawling and lets the LLM author from what you provide — fast, best when you already have the facts or just want a quick draft. When your inputs are sparse (few/no options, no domains, no seedData), prefer 'research' — it will discover and ground the comparison for you and yield a far stronger page than 'simple'. `seedData` (simple mode): paste your own raw facts/notes/competitor details here and the LLM writes from them instead of crawling — this is how you feed your own data and avoid a crawl. Async — fires the create, then polls the operation up to ~5 min. On success returns { briefId, sidePageId, sidePageSlug, landingPageSlug, webUrl, warnings }. If it is still running after the wait, returns { status: 'still_generating', operationId } — poll get_job with that operationId until state is 'completed'; do NOT fabricate the page yourself. Any `warnings` are surfaced verbatim — relay them to the user (e.g. sparse-input notes such as 'research mode would produce a stronger page').
list_api_keysList all API keys on the account. Shows prefix, scope, and revocation status. Does NOT show raw tokens. Lists default short; pass detail=medium/full for more fields.
create_api_keyCreate a new PostKing API key. The raw token (pk_live_*) is returned ONCE in this response and never shown again. Store it immediately — treat it like a password. Scope: 'write' (default) or 'read'.
revoke_api_keyPermanently revoke an API key. Pass confirm: true to proceed — this is irreversible and any clients using this key will stop working immediately.
list_jobsTo check a SPECIFIC operation's status, call get_job with its operationId — this list only returns the most recent ops and may omit a just-started one. List background jobs for the active brand. Use status='pending' to see in-flight ops, 'completed' to see finished ones. Use get_job with an operationId to poll a specific job — most async tools return an operationId. Supports detail param: short=id+kind+state, medium=6 key fields, full=raw.
list_operationsTo check a SPECIFIC operation's status, call get_job with its operationId — this list only returns the most recent ops and may omit a just-started one. List recent Operations (the newer async-op system) for the active brand. Each operation has: id, kind, state (pending|running|completed|partially_failed|failed|cancelled), progress, result, errors. Use get_job with an operationId to poll a specific one. Filters: kind (e.g. seo_keyword_generate, seo_cluster_generate, lp_generate), state. Supports detail param: short=id+kind+state, medium=adds scopeId+progress+timestamps (no result/errors), full=raw including result.
get_jobTo check whether ONE specific operation you started is finished, pending, or failed, call this with its operationId (the `pollUrl` param accepts a bare operationId + brandId). Do NOT use list_operations to check a specific op. Poll the status of any background Operation by its operationId or pollUrl. Returns the Operation row: { id, kind, state (pending|running|completed|partially_failed|failed|cancelled), brandId, scopeType, scopeId, progress, result, errors, startedAt, finishedAt, createdAt, updatedAt }. Call repeatedly until state is 'completed' or 'failed' (or 'cancelled'). When completed, the payload you want is in `result`; on failure, see `errors`. Pass wait:true to block until the job is done (polls every 3s, up to ~2 min) — preferred over calling repeatedly. Most generate_* and vibe_edit_* tools (including seo_generate_clusters and seo_generate_keywords) return an operationId — use this to poll them. Supports detail param: short=id+kind+state+progress, medium=adds timestamps+resultRef (key IDs from result, no full payload), full=raw including complete result JSONB.
get_weekly_scheduleRetrieve the current weekly content schedule for the active brand. Returns enabled status, lead time, timezone, and per-day platform configs. If no schedule is configured yet, returns suggested defaults. Includes a viewInBrowser link to open the calendar page in the app.
set_weekly_scheduleCreate or replace the weekly content schedule for the active brand. dayConfigs: array of { dayOfWeek (0=Sun…6=Sat), mediums: [{ medium, postsPerDay }] }. Mediums: x/twitter | linkedin | instagram | facebook | threads | blog. After setting, call enable_weekly_schedule to activate it.
enable_weekly_scheduleEnable the weekly content schedule without changing its configuration. The schedule must already be created with set_weekly_schedule.
disable_weekly_schedulePause the weekly content schedule without deleting it. Re-enable later with enable_weekly_schedule.
delete_weekly_schedulePermanently remove the weekly schedule for the active brand. Pass confirm: true to proceed.
run_weekly_schedule_dayTrigger the smart-week content generation engine for a specific date. This immediately queues posts for that day's schedule configuration. Use YYYY-MM-DD format for the date. Returns postsCreated count.
list_assetsList assets in the brand's visual library. Filter by type (IMAGE|DOCUMENT|VIDEO|LINK|LOTTIE), tags, or search text. Supports detail param: short=id+type+name, medium=key fields, full=raw.
view_assetView details of a single asset by ID. Supports detail param: short=id+type+name, medium=key fields, full=raw.
upload_assetUpload an asset to the brand library from a local file path or base64-encoded content. Prefer filePath for local files: the server reads and base64-encodes the file itself, avoiding truncation of large base64 strings over the tool_call boundary. fileBase64 is still supported for remote/inline use where no local path is available. For large files over the remote/HTTP transport, a single fileBase64 string can get truncated crossing the LLM→tool_call boundary — use the chunked flow instead: upload_asset_begin → upload_asset_chunk (× N) → upload_asset_finish. Provide exactly one of filePath or fileBase64. Returns the new asset ID and URL.
upload_asset_beginStart a chunked asset upload. Use this instead of upload_asset's fileBase64 param for large files over the remote/HTTP transport, where a single large base64 string can get truncated crossing the LLM→tool_call boundary. Flow: upload_asset_begin (once) → upload_asset_chunk (once per chunk, in order) → upload_asset_finish (once). Returns an uploadId that expires after 10 minutes of inactivity.
upload_asset_chunkSend one chunk of a base64-encoded file previously started with upload_asset_begin. Chunks must be sent in order, index starting at 0, with no gaps.
upload_asset_finishFinalize a chunked asset upload: reassembles the buffered chunks, verifies integrity, and uploads the asset to the brand library. Returns the new asset ID and URL.
upload_asset_abortCancel a chunked asset upload in progress and discard any buffered chunks.
import_asset_from_urlImport an asset into the brand library from a public URL. The server fetches and stores the file. Set assetType (e.g. 'google-image') when importing a result surfaced by search_web_images — it is recorded as a tag on the asset to preserve provenance.
import_assets_csvBatch-import up to 50 assets by providing an array of public URLs. All are added to the brand library. Supports detail param for the returned asset list.
tag_assetAdd or remove tags on an asset. Provide addTags and/or removeTags as arrays.
delete_assetSoft-delete an asset from the brand library. Pass confirm: true to proceed.
list_asset_tagsList all unique tags used across the brand's asset library.
suggest_assets_for_postGet AI-suggested assets from the brand library that match a given post context or topic.
search_stock_imagesSearch stock photo/video libraries for images matching a query. Returns URLs and descriptions. Use import_asset_from_url to add a result to the library. Supports detail param: short=url+thumbnail, medium=adds description+credit, full=raw.
generate_post_visual_optionsFetch available visual options for a post — card templates, library matches, stock photos. Returns a bestPick recommendation plus categorized options per platform. Use pick_post_visual to apply one of the returned options. Returns slim option list with pickArgs by default (medium). Use detail='short' for counts only, 'full' for raw catalog. Includes editInVisualEditor: a direct URL to edit the post in the visual editor (when active brand is set).
regenerate_post_visualRegenerate the visual option set for a post — refreshes stock photo results and re-scores library assets. Returns slim option list with pickArgs by default (medium). Use detail='short' for counts only, 'full' for raw catalog. Includes editInVisualEditor: a direct URL to edit the post in the visual editor (when active brand is set).
pick_post_visualSelect a visual for a post on a given platform. Use the chosen option's `pickArgs` from generate_post_visual_options VERBATIM — for card/quote templates that means passing kind + style + variant together; for a library/smart asset or a stock photo, pass the assetId or slot from its pickArgs. Do not invent style names. variant is a 1-based template variant index. Includes editInVisualEditor: a direct URL to edit the post in the visual editor (when active brand is set).
clear_post_visualRemove the selected visual from a post for a specific platform. Includes editInVisualEditor: a direct URL to edit the post in the visual editor (when active brand is set).
list_post_cardsList the carousel cards attached to a post. Cards are used for LinkedIn carousel / PDF generation. Returns {index,title} by default; use detail='medium' for truncated body, 'full' for all fields.
edit_post_cardEdit a single carousel card on a post by its 1-based index. Provide title and/or body to update. Set rerender=true to regenerate the visual asset.
set_post_cardsBulk-replace all carousel cards for a post. Provide a full array of card objects with title, body, and optional number.
generate_post_carouselGenerate a carousel PDF for a LinkedIn (or other) post from the post's cards. Returns an asset ID and download URL for the PDF. Requires cards to be set first via set_post_cards or edit_post_card.
search_web_imagesSearch Google Images across the whole web for a query — broader than search_stock_images, which only searches licensed stock photo/video libraries. Returns image URLs, the source site, and a link back to the source page. openLicensedOnly is a best-effort source filter, not a legal license guarantee — agents and users should still verify usage rights before publishing any result. Use import_asset_from_url to add a chosen result to the library. Supports detail param: short=url+source, medium=adds sourceUrl+alt+dimensions, full=raw.
web_searchPerform a live, real-time web search and get back a raw answer with sources — for questions like 'find me the top 10 places to share/index my MCP', 'what's the latest on X', or 'where can I find Y'. Distinct from search_web_images, which only returns images — this tool returns a synthesized text answer plus the sources it drew from (each with title, url, and optional description), and optionally related follow-up prompts. Results are returned as-is (unsummarized) — pass the answer and sources straight through to the user.
list_landing_pagesLists landing pages. Default detail='short' (id/slug/name/status). Use view_landing_page for full content.
generate_landing_pageCreate and AI-generate a new landing page for the brand. Step 1: Creates the LP record with the given slug. Step 2: Kicks off async AI content generation immediately. Returns { slug, operationId, pollUrl } — poll with get_job(operationId) until state is 'completed' (or 'failed'/'partially_failed'/'cancelled' on error).
view_landing_pageFetch a landing page by slug. detail='full' (default) returns full data JSONB; 'medium' returns summary + sectionKeys/sectionWordCounts; 'short' returns id/slug/name/status. Section bodies and rendered HTML appear only at full.
edit_landing_pageUpdate the title or instructions of a landing page. For AI-powered edits, use vibe_edit_landing_page.
set_landing_pageOverwrite the content and/or metadata of a landing page. Pass content as a string (HTML or markdown). Pass metadata as a JSON object. Returns a versionId — all writes are versioned.
regenerate_landing_pageRe-generate a landing page's content using AI. Optionally restrict to specific sections. Returns an operationId — poll with get_job to track progress.
vibe_edit_landing_pageUse AI to edit a landing page based on natural-language instructions. Returns an operationId — poll with get_vibe_edit_status or get_job until status is 'completed'. Optionally limit to a specific scope ('headline' | 'cta' | 'full') or a single sectionId.
get_vibe_edit_statusPoll vibe (AI) edit status. detail='full' (default) includes the result payload; 'short'/'medium' return just state+progress.
publish_landing_pagePublish a landing page, making it publicly accessible at its URL.
delete_landing_pagePermanently delete a landing page. Pass confirm: true to proceed — this is irreversible.
view_lp_draftView the unpublished draft of a landing page. detail='full' (default) includes full versionData; 'medium' adds sectionKeys/sectionWordCounts; 'short' is id/slug/name/status only.
list_lp_versionsList all saved versions of a landing page. Default detail='short'. Use view_lp_version to see section content.
view_lp_versionView a specific LP version. detail='full' (default) returns full data; 'medium' adds sectionKeys/sectionWordCounts.
list_side_pagesList side pages attached to a landing page. Default detail='short'. Heavy JSONB (overrides/config) only at full via view_side_page.
generate_side_pageAI-generates a side page under a parent landing page. Async — kicks off the side-page generator and returns `{ success, operationId, operationRowId, pollUrl, sidePageId }`. This is the GENERATOR (POST /side-pages/generate) — NOT a row creator. Comparison-type briefs may run synchronously and return `sidePageId` directly with no operationId. Two body modes: • freeform: pass `key` + `prompt` (+ optional `keywords`, `selectedSections`, `voiceProfileId`, `sidePageType`). • brief: pass `key` + `brief` (structured outline) + optional `briefId` and `roadmapItemId`. Poll `get_job` until `state` is `completed` (or `failed`/`partially_failed`/`cancelled` on error).
view_side_pageView a side page including sections and rendered HTML. detail='full' (default) includes rendered HTML and full overrides; 'medium' gives summary + overrideSectionKeys; 'short' gives id/slug/name/type/isPublished. Rendered HTML appears only at full.
edit_side_pageUpdate the instructions or metadata of a side page. For section-level edits, use set_side_page_section.
delete_side_pageDelete a side page. Pass confirm: true to proceed.
set_side_page_sectionUpdate the content of a specific section within a side page.
set_side_page_statePublish or unpublish a side page. Set published=true to make it live, false to pull it back to draft.
dashboard_linkReturn a clickable browser link to a PostKing dashboard page. ALWAYS use this instead of guessing dashboard URLs. The SEO roadmap / content plan is section 'seo_briefs' (or 'seo' for the overview) — there is NO '/seo/roadmap' page.
reddit_get_poolReturns the brand's pool of relevant subreddits — THIS IS the brand-level subreddit match (each scored). Use it to answer 'which/what/top N subreddits should my brand post in?' — NO content needed; results are sorted most-relevant first; pass `top` for a top-N list. (reddit_suggest is a different, content-specific step.) Reddit is a repurpose-to-Reddit workflow, NOT a scheduled publishing medium.
reddit_generate_poolKick off async generation of a subreddit pool for the brand — finds relevant subreddits by crawling Reddit. Typically takes ~1–3 min. Returns { operationId, status }. Poll get_job with the operationId until state=completed, then call reddit_get_pool to see results. Reddit is a repurpose-to-Reddit workflow, NOT a scheduled publishing medium.
reddit_global_poolReturn stats on the global subreddit dataset (count of known subreddits available for matching). Informational only — no DB writes.
reddit_suggestGiven a brand's content (a blog post by id, or pasted title+text), return up to 8 best-fit subreddits from the brand's pool, each with 2-3 distinct posting angles (angle type + tailored title + framing hook), plus promotion mode, buyer intent, match score, and the key rule to watch. Use an angle's title/hook to then draft a native post via reddit_rewrite. short {subreddit,match_score,promotion_mode,buyer_intent,angle} (angle = first angle only); medium adds reason,rule_to_watch,angles (all angles); full = raw. Synchronous, 0 credits. Requires the brand pool to exist — call reddit_generate_pool first if it doesn't. Flow step 2 of 4: pool → SUGGEST → rewrite → list_posts.
reddit_rewriteAsync. Rewrite a blog article (or raw content) into a Reddit-native post for a specific subreddit. Typically takes ~30–90 sec per variation. This tool polls inline and returns the finished Reddit post once generation completes — you do NOT need to poll separately. If it times out before completing, it returns a postId; call get_post with that postId until operationStatus is COMPLETED. Requires pool to exist. The subreddit must be in the brand's pool. Flow step 3 of 4: pool → suggest → REWRITE → list_posts.
reddit_list_postsList saved Reddit posts (outputs of reddit_rewrite). Cursor-paginated. Returns { posts: [{ id, platform, content, outputData, sessionId, voiceId, createdAt }], nextCursor }. outputData contains: redditTitle, body, notes, wordCount, angle, length, subreddit, variationIndex. Flow step 4 of 4: pool → suggest → rewrite → LIST_POSTS.
storyline_listList the brand's storylines (marketing plans). short detail {id,title,status}; medium adds isLive, dates, promptSummary; full = raw.
storyline_createCreate a new storyline (marketing plan) for the brand. Pass a prompt describing the campaign goal; optionally provide a title. After creation, call storyline_clarify to gather context, then storyline_generate_brief.
storyline_getFetch a single storyline by ID with its full state (brief, strategy, line items, status). Returns full detail by default. Use detail="medium" for a compact summary or detail="short" for {id,title,status}.
storyline_updateUpdate metadata on a storyline: title, live status, or start/end/launch dates. Pass at least one field to change.
storyline_deleteArchive (soft-delete) a storyline. Pass confirm: true to proceed. Use storyline_restore to reverse this.
storyline_restoreRestore an archived storyline back to active state.
storyline_clarifyRun the intake/clarification step for a storyline. The API returns follow-up questions or a readiness signal; call iteratively until the system has enough context. After clarification is complete, call storyline_generate_brief.
storyline_generate_briefAsync. Generate the marketing brief for a storyline (positioning, key messages, audience, timing, tone notes). Returns { operationId, status } — poll get_job with the operationId until state=completed. Typically takes ~1–3 min. After completion, review the brief with storyline_get, then call storyline_confirm_brief to advance to strategy.
storyline_set_briefManually set (replace) the full brief for a storyline. Use to provide a human-authored brief or to push back an edited version retrieved via storyline_get. Pass the complete brief object and the current expectedVersion (use 0 when setting from scratch). After setting, call storyline_confirm_brief to advance to strategy generation.
storyline_edit_briefApply an AI-driven edit to the current brief using a natural-language instruction. Examples: 'Make the tone more casual', 'Add a proof point about our 99% uptime SLA'. Optionally pass expectedVersion for optimistic concurrency.
storyline_confirm_briefConfirm (lock) the brief for a storyline, advancing it to the strategy phase. After confirmation, call storyline_generate_strategy.
storyline_get_strategyFetch the strategy and line items for a storyline. Returns full detail by default (raw strategy + all line items). Use detail="medium" for a compact summary or detail="short" for {id,status} + line-item count.
storyline_generate_strategyAsync. Generate the strategy and line-items for a storyline based on its confirmed brief. Returns { operationId, status } — poll get_job with the operationId until state=completed. Typically takes ~2–5 min. After completion, review with storyline_get_strategy, then optionally edit with storyline_edit_strategy or add/remove line items.
storyline_edit_strategyApply an AI-driven edit to the current strategy using a natural-language instruction. Examples: 'Add a LinkedIn video post for launch week', 'Remove the influencer outreach line items'.
storyline_estimateRead-only dry-run. Estimate the credits required to execute the storyline without actually running it. Use before storyline_execute to surface the cost to the user for approval. Returns { estimatedCredits, lineItemBreakdown } or similar.
storyline_add_line_itemAdd a new line item (deliverable) to a storyline's strategy. Specify the channel, type, title, description, and a config map (pass {} if no extra config).
storyline_update_line_itemUpdate a line item on a storyline — select/deselect, retitle, change description, targetDate, or config. Pass only the fields to change.
storyline_delete_line_itemPermanently remove a line item from a storyline's strategy. Pass confirm: true to proceed.
storyline_regenerate_line_itemAsync. Re-generate a single line item's content draft. Returns { operationId, status } — poll get_job with the operationId until state=completed. Typically takes ~1–3 min.
storyline_executeAsync. Execute a storyline — generates content drafts for all selected line items. Returns { operationId, status } — poll get_job with the operationId until state=completed. Typically takes ~3–8 min. Call storyline_estimate first to surface the credit cost before execution.
competitor_listList the brand's tracked competitors. short {id,domain,analysisState}; medium adds source,creditsCharged,lastError,addedAt,lastCrawledAt,cacheSource; full = raw. Also returns a dashboard link to the Competitors tab.
competitor_addAsync. Batch-add competitor domains (1–20) to the brand. Returns { operationId, status } — poll get_job until state=completed. Each domain triggers crawl + profile analysis. Typically takes ~2–5 min.
competitor_updateUpdate a competitor's settings. Currently supports toggling excludeFromSeoPull (removes the domain from keyword-gap pull without deleting it). Send an empty body to restore a soft-deleted competitor.
competitor_deleteSoft-delete a tracked competitor from the brand. No credits are refunded. Use competitor_update (empty body) to restore.
competitor_analyzeAsync. Trigger analysis for existing BrandCompetitor rows that are pending or failed. Use competitor_add to create new rows; use this to retry failed ones. Returns { operationId, status } — poll get_job until state=completed. Typically takes ~2–5 min.
competitor_refreshAsync. Refresh all active competitors for the brand (re-crawl + re-profile). Returns { operationId, status } — poll get_job until state=completed. Typically takes ~2–5 min.
competitor_get_comparisonGet the brand's head-to-head competitive comparison. short {id,status,generatedAt,competitorCount}; medium adds summary+strengths+weaknesses; full = raw. Returns null when no comparison has been generated yet — use competitor_recompute_comparison to generate.
competitor_recompute_comparisonTrigger a fresh head-to-head comparison recompute. Use after adding or re-analyzing competitors to get an up-to-date comparison.
competitor_get_overviewGet the brand's competitive landscape overview. short {id,status,generatedAt}; medium adds summary excerpt; full = raw. Returns null when no overview exists — use competitor_generate_overview to create one.
competitor_generate_overviewAsync. Generate the competitive landscape overview (uses ~20 credits). Returns { operationId, status } — poll get_job until state=completed. Typically takes ~2–5 min.
competitor_comparison_sourcesList the data sources used to build the brand's competitive comparison. Returns raw source records (URLs, snippets, timestamps) — useful for auditing comparison accuracy.
competitor_probeStart a competitor discovery probe. PostKing crawls the web to find rival domains automatically. Returns { started: true } when kicked off, or { alreadyRan, status } when a probe result already exists. Poll competitor_probe_status to check readiness, then use competitor_probe_classify to accept/reject candidates.
competitor_probe_statusCheck the status of the competitor discovery probe. Returns { status, candidates? } — status is one of: pending | running | completed | failed. When completed, candidates contains the discovered domains ready for classification.
competitor_probe_classifyClassify a discovered (or manually added) competitor candidate. 'direct' seeds a BrandCompetitor row; 'similar' and 'not_relevant' update the probe JSON only. Call once per domain. Probe must be in completed state first. Returns { candidates } — the updated full candidate list.
knowledge_listList the brand's knowledge-base items. short {id,name,contentType}; medium adds tags+summary+timestamps; full = raw. Filter by tag, active status, or global scope.
knowledge_createAsync. Create a new knowledge-base item for the brand. Returns { operationId, status } — poll get_job until state=completed. If description or tags are omitted, PostKing auto-generates them from the content. For contentType='json', content must be valid JSON — this tool validates client-side before calling the API. Typically takes ~15–30 s.
knowledge_getFetch a single knowledge-base item by ID. short {id,name,contentType}; medium adds tags+summary+timestamps; full = raw (includes full content). Use detail='full' to retrieve the complete content body.
knowledge_updateUpdate a knowledge-base item. Minor edits (name, tags, description) return the updated item synchronously. When content changes significantly, PostKing queues an AI description regeneration and returns { operationId, status } — poll get_job until state=completed. For contentType='json', content must be valid JSON — this tool validates client-side before calling the API. Typically takes ~15–30 s.
knowledge_deleteSoft-delete a knowledge-base item. The item is deactivated (isActive=false) and no longer appears in knowledge_list. This action is not reversible via the API.
brand_truth_listList the brand's stored brand truths (atomic facts/observations used to ground generation). short {id,name,type,pinned}; medium adds personaScope+tags+summary+timestamps; full = raw. Filter by type, personaScope, tags (array or comma-separated), or a free-text query.
brand_truth_getFetch a single brand truth by ID. short {id,name,type,pinned}; medium adds personaScope+tags+summary+timestamps; full = raw (includes full content). Use detail='full' to retrieve the complete content body.
brand_truth_createCapture brand truths from plain natural-language text. Describe facts/observations about the brand in ordinary prose — a sentence or short paragraph (≤8000 chars). Do NOT pre-classify, pre-format, or guess the taxonomy: PostKing's LLM extraction pipeline reads the text and decides which atomic 'brand truths' to persist and which to skip (duplicates, too vague, or previously rejected facts). Returns { addedCount, skippedCount, added, skipped }: 'added' are the truths that were stored; 'skipped' lists each rejected quote with a reason. Review both — the skipped reasons tell you what didn't make it in and why.
brand_truth_updateTargeted edit of an existing, known brand truth (by ID). This does NOT re-run the LLM extraction pipeline — it writes the provided fields directly. Use it to correct wording (name/description/content), fix the type/personaScope, adjust tags, or pin/unpin. To capture NEW facts from prose, use brand_truth_create instead.
brand_truth_deleteDelete a brand truth by ID. This also records rejection memory: the system learns to stop re-suggesting that fact during future extractions. Use it deliberately — deleting a truth teaches PostKing that the fact should not come back.
get_audienceFetch the brand's audience intelligence / ICP (ideal customer profile). short = compact summary (name + primaryRoles + top painPoints + persona.role); medium adds positioning + fuller demographics; full = the raw payload (audienceData + positioning + persona + contentModulation). `persona` is the ghostwriter persona ({ role, styleNotes, ... }) and may be null. If the brand has no audience data yet, run website/audience analysis (onboarding) first.
preview_audience_editRead-only helper. Call this BEFORE edit_audience to discover which `sections`/`subsections` values are valid for this brand. Pass the natural-language change you intend to make; returns the available sections/subsections (computed from the brand's current audience data) plus a preview. Use the returned section keys (e.g. 'demographics', 'painPoints', 'positioning') as the required `sections` array for edit_audience.
edit_audienceAsync LLM ai-edit of the brand's audience/ICP. Describe the change in `prompt` (natural language). `sections` is REQUIRED — the audience section(s) to edit (e.g. 'demographics', 'painPoints', 'positioning'). If unsure which sections are valid for this brand, call preview_audience_edit first and use the section keys it returns. Returns { operationId, status } — poll get_job(operationId) until state is 'completed' (or 'failed'/'cancelled' on error). Only one audience edit can run at a time; a second call returns an 'already_running' notice. Typically takes ~30–90 s.
trends_listBrowse top-trending posts (with deconstructions) for a niche + platform. Account/niche-scoped — NOT tied to a specific brand. Each post includes hook, template, pattern, and virality reason from the deconstruction. The crawler runs every 3 days; use days=3 (default) for the freshest batch. Supported niches: ai-saas, marketing, web3. Supported platforms: x.
template_listList the brand's saved content templates. short {id,title,category}; medium adds platforms,isFavorite,bodyPreview (160 chars); full = raw. Pass category to filter (e.g. 'hook', 'cta', 'thread'). Results are ordered by isFavorite desc, then usageCount desc.
template_createCreate one or more content templates for the brand. Pass a single template object, or pass the 'templates' array param for bulk creation. If both are supplied, 'templates' (bulk) takes precedence. Returns the created template record(s).
template_updateUpdate an existing content template. All fields are optional — only supplied fields are changed. Use isFavorite=true/false to toggle favorite status.
template_deletePermanently delete a content template from the brand. This action is irreversible.
template_extractAI extracts a reusable content template from a pasted post text. Synchronous (seconds) — no polling needed. Pass save=true to also persist the template to the brand's library. Returns the extracted template object; if saved, includes the new template id.
template_pickRE-RANKER: AI scores a caller-supplied list of candidate templates and picks the N best-fitting ones for a given theme or topic. This tool does NOT read stored templates server-side — the caller must supply the candidates explicitly (e.g. call template_list first, then pass the results here). Synchronous — no polling needed. Pass the templates array from template_list (full detail) as candidates. Returns { templateIds } — an ordered array of the winning template IDs.
billing_list_packsList available credit packs for one-off top-ups. Returns all packs with their SKU, price in USD, and credit amount. Call this tool first to show the user their options, then ask which pack they want. Only after the user explicitly chooses a pack, call billing_topup with that packSku.
billing_topupTop up credits by charging the account's card on file (Stripe off-session). Prefers the headless path — no checkout link required. IMPORTANT: Only call this tool after the USER has explicitly chosen a specific pack — it triggers a real charge. To show the user their options first, call billing_list_packs and present the results; do NOT pick a pack on the user's behalf. The response is ONE OF two shapes: (1) Headless success (default when a card is on file): { status: 'paid', paymentIntentId, amountUsd, credits, balance, packSku, cardLast4/receiptUrl when available }. When you receive status === 'paid', the payment has already completed and the credits are in the wallet NOW. Announce to the user: payment ID, last-4 card digits, credits added, and new balance. You are DONE — do NOT call billing_wallet to poll. (2) Checkout fallback (only when there is no card on file): { checkoutUrl, sessionId, amountUsd, credits, packSku }. When you receive checkoutUrl, hand that link to the user so they can complete payment in their browser. Valid skus: agent_4 ($4 / 160 credits), agent_5 ($5 / 220 credits), agent_25 ($25 / 1200 credits), agent_50 ($50 / 2600 credits).
billing_walletFetch the user's credit balance and recent usage entries. Returns { credits, recent } where recent is the last ~10 usage rows. Poll this to confirm a top-up landed ONLY after a billing_topup CHECKOUT result (one that returned a checkoutUrl), until credits rise. Do NOT poll after a status:'paid' headless top-up — those credits are already applied and the new balance is in the topup response.
billing_list_tiersList available PostKing subscription tiers (GROWTH, PRO, ENTERPRISE). Returns each tier's name, price in USD, monthly credits, and billing interval options. Use billing_subscribe to create a subscription Checkout session for a chosen tier.
billing_subscribeCreate a Stripe Checkout session for a PostKing subscription. Returns { checkoutUrl, sessionId, tier, interval, amountUsd }. Subscription credits refill User.credits each billing period. The subscription Checkout is best completed by a human; the Link virtual card covers the first invoice only (renewals need a durable payment method).
Automated checks
Ran Nov 13, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablebitsandtea/postking-mcp is public and reachablegithub.com/bitsandtea/postking-mcp ↗Pass
- Package names this repository as its sourcepostking-mcp names bitsandtea/postking-mcp as sourcenpmjs.com/package/postking-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-12github.com/bitsandtea/postking-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packagepostking-mcp looks like @conorbronsdon/postlint-mcpFinding
- No critical advisory in the package or its dependencies100 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model5 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubPostKing MCP Server
The official Model Context Protocol server for PostKing — an AI-powered content platform for social media scheduling, blog publishing, and brand management.
Connect Claude (Desktop, Cursor, or any MCP client) to your PostKing account and manage your entire content operation through conversation — generate posts, schedule them, repurpose URLs into social content, write and publish blog articles, generate landing pages and side pages, run SEO / GEO research and drafting, manage your asset library and weekly posting schedule, handle domains and API keys, and more.
The server exposes 291 tools across 33 modules — full parity with the postking-cli.
Transport note: All 291 tools are registered on both transports, including on the remote HTTP transport (
mcp.postking.app). The 4 authentication tools (login_start,login_complete,logout,whoami) stay registered there too — they just explain the OAuth bearer-token model instead of running a device-code flow, since that transport is already authenticated before any tool call happens.
Quick start
Claude Desktop
Option A — Via the GUI:
- Open Claude Desktop → Settings (gear icon) → Developer → Edit Config
- This opens
claude_desktop_config.jsonin your default editor - Paste the following and save:
{
"mcpServers": {
"postking": {
"command": "npx",
"args": ["-y", "postking-mcp"]
}
}
}
- Restart Claude Desktop
Option B — Edit the config file directly:
Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) in any text editor, paste the same JSON above, and save.
Once restarted, tell Claude: "Login to PostKing"
Claude Code (CLI)
claude mcp add postking -- npx -y postking-mcp
Hermes
npm i -g postking-mcp
hermes mcp add postking --command postking-mcp
Then in Hermes: "Login to PostKing".
Cursor / other MCP clients
Use the same npx -y postking-mcp command in your client's MCP server config.
Login flow
No API keys to copy. PostKing uses a device login flow:
- Tell Claude: "Login to PostKing"
- Claude calls
login_start→ shows a URL and short code - Visit the URL in your browser, log in, approve
- Tell Claude: "Done"
- Claude calls
login_complete→ saves your token to~/.postking/credentials.json
You never need to log in again. The token is permanent.
What you can do
Authentication
Available on stdio/local transport only. Remote HTTP transport authenticates via OAuth bearer token before the session is created.
| Tool | Description |
|---|---|
login_start |
Begin device login — get a URL and code to approve in browser |
login_complete |
Finish login and save token after browser approval |
logout |
Clear locally stored credentials |
whoami |
Return the profile of the currently authenticated user (email, plan, credit balance) |
Brands
| Tool | Description |
|---|---|
list_brands |
List all brands on your account |
set_active_brand |
Set the default brand for this session |
get_brand_info |
View brand profile — tone, audience, themes |
create_brand |
Create a brand manually (step 1 of manual onboarding) |
onboard_brand |
Crawl a website and auto-generate a brand profile + 10 themes (step 1 of website onboarding) |
set_brand_mediums |
Save the list of platforms the brand publishes on (step 2 of onboarding) |
get_brand_mediums |
Read which publishing platforms a brand posts to |
get_business_type |
Read what the brand sells (software, product, local business, service) for structured data |
set_business_type |
Set the business type (or reset: true to re-detect) |
get_brand_content_language |
Read the language a brand's AI-generated content is written in, plus the supported set |
set_brand_content_language |
Set the generation language for all future content — en, es, pt-BR, de, fr, cs |
get_onboarding_status |
Poll background audience analysis + theme generation (step 3 of onboarding) |
Content themes
| Tool | Description |
|---|---|
list_themes |
List all content themes with IDs |
generate_themes |
AI-generate new themes (uses credits) |
edit_theme |
Update a theme's title or instructions |
delete_theme |
Remove a theme |
Social posts
| Tool | Description |
|---|---|
generate_post |
AI-generate a post for a platform |
create_post |
Save a manual post draft to one or more platforms |
list_posts |
List posts filtered by status or platform |
get_post |
View a single post |
approve_post |
Approve and schedule a draft post |
schedule_post |
Set a scheduled time on an existing post |
reschedule_post |
Move a scheduled post to a new time |
update_post |
Replace a draft or scheduled post's text |
reply_to_x_post |
Reply to an X (Twitter) post from the brand's account (PRO plan and above) |
cancel_post |
Cancel a scheduled post without deleting it |
delete_post |
Cancel and delete a post |
get_calendar |
View upcoming scheduled content |
generate_bulk_posts |
Fill a date range with AI-generated posts |
Repurpose
| Tool | Description |
|---|---|
repurpose_content |
Turn a URL, text, or existing post into new social or blog content |
Voice profiles
| Tool | Description |
|---|---|
list_voices |
List available voice profiles |
rewrite_with_voice |
Rewrite text in a specific voice |
Social accounts
| Tool | Description |
|---|---|
check_social_accounts |
List connected and disconnected platforms |
generate_connect_link |
Get a secure OAuth link to connect a platform |
disconnect_social_account |
Disconnect a social account |
Reddit is a repurpose-to-Reddit workflow, not a scheduled publishing medium. Flow: reddit_generate_pool → reddit_get_pool → reddit_suggest → reddit_rewrite → reddit_list_posts.
| Tool | Description |
|---|---|
reddit_get_pool |
View the brand's saved pool of relevant subreddits, sorted by relevance score |
reddit_generate_pool |
Async: discover and score relevant subreddits for the brand by crawling Reddit |
reddit_global_pool |
Return stats on the global subreddit dataset (informational only) |
reddit_discover_subreddits |
Sync: search Reddit for subreddits by user-directed queries (with free-text disambiguation context), ranked by subscribers and flagged against the brand pool — 15 credits per call |
reddit_add_to_pool |
Add subreddits to the brand's pool by name (resolves live from Reddit; partial success reported per name) — free |
reddit_remove_from_pool |
Remove subreddits from the brand's pool by name (brand-scoped only; never touches the global cache) — free |
reddit_suggest |
Sync: suggest up to 8 best-fit subreddits for a specific piece of content, each with 2-3 posting angles, promotion mode, and buyer intent |
reddit_rewrite |
Async: rewrite a blog article or raw content as a native Reddit post for a target subreddit |
reddit_list_posts |
List saved Reddit posts (outputs of reddit_rewrite), cursor-paginated |
Blog
| Tool | Description |
|---|---|
list_blogs |
List publications and articles (filterable by status) |
list_publications |
List publications only |
create_publication |
Create a new blog publication |
update_publication |
Update an existing publication's title, description, domain/routing, or layout (partial update) |
generate_blog_post |
AI-generate a full blog article with optional voice |
get_blog_article |
Fetch full article content, including the featured/header image (featuredImageUrl, featuredImageAlt, featuredImageDescription) |
get_blog_status |
Poll generation/publish status for an article |
update_blog_article |
Edit title, content, SEO fields, author, category, status, or the featured/header image (featuredImageUrl, featuredImageAlt, featuredImageDescription) |
delete_blog_article |
Permanently delete an article |
blog_cta_list |
List every CTA on an article individually, with raw anchor data — find a ctaId or an open anchor slot |
blog_cta_add |
Append a new CTA to an article without touching the existing ones |
blog_cta_update |
Edit one CTA by id (url/label/headline/body/style/anchor/sidePageId/slug) without touching the others |
blog_cta_delete |
Remove one CTA by id without touching the others |
publish_blog_article |
Push to WordPress, Medium, Substack, etc. |
list_publishing_connections |
List external platform connections |
import_blog_articles |
Import from RSS feed or Blogger URL |
list_blog_authors |
List blog authors |
create_blog_author |
Create a new blog author |
get_side_page_author_defaults |
Read who is credited as author on comparison / feature side pages |
set_side_page_author_defaults |
Set the per-kind side-page author (author id, "none", or null = blog default) |
list_blog_categories |
List categories for a publication |
create_blog_category |
Create a new category |
get_seo_roadmap |
View SEO / GEO topic suggestions and completion stats |
SEO / GEO
Canonical flow: seo_add_seeds → seo_generate_keywords → seo_categorize → seo_generate_clusters → approve clusters → seo_generate_roadmap → review briefs → seo_approve_briefs (auto-fires article generation) → poll get_job → audit & publish.
| Tool | Description |
|---|---|
seo_add_seeds |
Seed SEO / GEO research with 3–10 topic keywords |
seo_generate_keywords |
Async: expand seeds into a full keyword universe (poll via get_job) |
seo_list_keywords |
List researched keywords with intent, priority, and volume |
seo_edit_keyword |
Edit a keyword — override intent, adjust priority, set user tags, or exclude from clustering |
seo_delete_keyword |
Soft-delete a single keyword from the research set |
seo_categorize |
Tag keywords by search intent and/or user tags |
seo_generate_clusters |
Async: group keywords into topic clusters (poll via get_job) |
seo_list_clusters |
List keyword clusters with brief-generation status |
seo_bulk_approve_clusters |
Bulk-approve N clusters in one call, kicking off async brief generation for each |
seo_approve_cluster |
Approve a single cluster, gating brief generation for it |
seo_reject_cluster |
Reject a single cluster — marks it rejected and detaches its keywords |
seo_bulk_reject_clusters |
Bulk-reject N clusters in one call |
seo_unapprove_cluster |
Revert an approved cluster back to pending_review |
seo_restore_cluster |
Restore a rejected cluster back to pending_review |
seo_generate_roadmap |
Turn one or more clusters into a prioritized content roadmap |
seo_list_roadmap |
List roadmap items (blog topics queued for writing) |
seo_roadmap_get |
Fetch a single roadmap item |
seo_roadmap_edit |
Change a roadmap item's status, or restore / pin / unpin / remove it; start on a refresh item rewrites its page |
seo_search_data_status |
Search Console / Bing connected? Last roadmap reconcile + refresh / hidden counts |
seo_search_data_reconcile |
Re-run the search-data roadmap reconcile now (async) |
seo_roadmap_delete |
Permanently delete a roadmap item |
seo_roadmap_stats |
Roadmap completion stats |
seo_list_briefs |
List content briefs across all clusters and statuses |
seo_get_brief |
Fetch a single brief including its full structured outline |
seo_edit_brief |
Edit a brief's structured outline or approve/reject it |
seo_approve_briefs |
Bulk-approve briefs and auto-fire article generation |
seo_regenerate_brief |
Re-run brief generation for a single brief |
seo_resolve_brief_truths |
Re-resolve the brand truths a brief's page is written from |
seo_list_results |
List generated results (blog articles, side pages, comparisons) from the SEO pipeline |
seo_write_article |
Manual path: draft a blog article from a roadmap item (use only when not going through seo_approve_briefs) |
seo_gap |
Find keyword / topic gaps vs. existing content |
seo_competitor |
Compare keyword coverage against a competitor domain |
seo_publish_article |
Publish or schedule an SEO-drafted article to a publication |
seo_auto_assign_cta |
Auto-suggest and assign side-page CTAs to published blog articles |
seo_generate_side_page |
Generate a side page optionally linked to an SEO cluster |
Landing pages
| Tool | Description |
|---|---|
list_landing_pages |
List all landing pages for a brand |
generate_landing_page |
Create and AI-generate a new landing page (async; poll via get_job) |
import_landing_page_bundle |
Import a static-build bundle (entry HTML + assets) hosted at URLs — for a local folder, use the postking-cli import-bundle command instead |
view_landing_page |
View a landing page including full section content |
view_lp_draft |
View the current unpublished draft |
edit_landing_page |
Edit landing page title or instructions (metadata only — does not touch page content) |
set_landing_page_section |
Set one field (dot-path) or replace a whole section on a landing page's draft |
regenerate_landing_page |
Re-generate a landing page's content using AI (async; poll via get_job) |
vibe_edit_landing_page |
Apply a natural-language AI edit to a landing page (async; propose → review → apply flow) |
get_vibe_edit_status |
Poll vibe-edit session status and review the field-level changes diff |
apply_vibe_edit |
Apply a completed vibe edit (all or a subset) to the draft as one new version |
set_lp_section_layout |
Reorder and/or toggle visibility of landing page sections |
publish_landing_page |
Publish the current draft |
delete_landing_page |
Permanently delete a landing page |
list_lp_versions |
List historical versions of a landing page |
view_lp_version |
View a specific historical version |
restore_lp_version |
Roll the draft back to a prior version |
delete_lp_version |
Permanently delete a historical version |
list_side_pages |
List side pages attached to a landing page |
generate_side_page |
AI-generate a side page under a parent landing page (async; poll via get_job) |
view_side_page |
View a side page including sections and rendered HTML |
edit_side_page |
Update the instructions, metadata or author (authorId/hideAuthor) of a side page |
set_side_page_section |
Update the content of a specific section within a side page |
set_side_page_state |
Publish or unpublish a side page |
delete_side_page |
Delete a side page |
Weekly schedule
| Tool | Description |
|---|---|
get_weekly_schedule |
Fetch the active weekly posting schedule |
set_weekly_schedule |
Configure platforms, times, and themes per day |
enable_weekly_schedule |
Turn the weekly auto-generator on |
disable_weekly_schedule |
Turn the weekly auto-generator off |
delete_weekly_schedule |
Remove the schedule entirely |
run_weekly_schedule_day |
Generate a single day's posts on demand |
Visuals (asset library)
| Tool | Description |
|---|---|
list_assets |
List brand assets (images/videos) with filters |
view_asset |
Fetch a single asset's metadata and URL |
upload_asset |
Upload an image/video (base64) |
import_asset_from_url |
Pull an asset from a remote URL |
import_assets_csv |
Batch-import up to 50 assets from a list of public URLs |
tag_asset |
Add or remove tags on an asset |
delete_asset |
Remove an asset (requires confirm) |
list_asset_tags |
List all tags used across assets |
suggest_assets_for_post |
Get AI-suggested assets for a specific post |
search_stock_images |
Search stock-photo libraries |
Post visuals (cards & carousels)
| Tool | Description |
|---|---|
generate_post_visual_options |
Fetch available visual options for a post (card templates, library matches, stock photos) |
regenerate_post_visual |
Refresh stock photos and quote/card templates for a post (does not re-match library assets) |
pick_post_visual |
Select a template/stock visual, or attach one or more of your own library assets, for a post on a given platform |
clear_post_visual |
Remove the selected visual from a post |
list_post_cards |
List the carousel cards attached to a post |
edit_post_card |
Edit a single carousel card by 1-based index |
set_post_cards |
Bulk-replace all carousel cards for a post |
generate_post_carousel |
Render a carousel PDF from the current cards |
Jobs (async poller)
| Tool | Description |
|---|---|
list_jobs |
List recent async jobs for the active brand |
list_operations |
List recent Operations (the newer async-op system) with kind and state filters |
get_job |
Poll a specific operation by ID or pollUrl; supports wait=true to block until done |
cancel_job |
Cancel a pending or running job/operation by operationId |
API keys (self-service)
| Tool | Description |
|---|---|
list_api_keys |
List your PostKing API keys |
create_api_key |
Mint a new API key |
revoke_api_key |
Revoke an API key (requires confirm) |
Domains
| Tool | Description |
|---|---|
list_domains |
List domains with verification and SSL status |
add_domain |
Add a new custom domain |
verify_domain |
Check DNS and activate a domain |
delete_domain |
Remove a domain (content is preserved) |
connect_domain_to_publication |
Wire a verified domain to a blog publication |
Writing tools
| Tool | Description |
|---|---|
rewrite_text |
Rewrite text using a voice profile or brand rules |
humanize_text |
Reduce AI detection signals in text |
check_ai_content |
Score text for AI detection likelihood |
get_credits |
Check your current credit balance and free-tier status |
health |
Check PostKing API health and version (no authentication required) |
Storylines (marketing plans)
Canonical flow: storyline_create → storyline_clarify (loop) → storyline_generate_brief (poll) → storyline_get → storyline_edit_brief → storyline_confirm_brief → storyline_generate_strategy (poll) → curate line items → storyline_estimate → storyline_execute (poll).
| Tool | Description |
|---|---|
storyline_list |
List the brand's storylines (marketing plans) |
storyline_create |
Create a new storyline with a campaign goal or intent prompt |
storyline_get |
Fetch a single storyline with full state (brief, strategy, line items, status) |
storyline_update |
Update storyline metadata: title, live status, or start/end/launch dates |
storyline_delete |
Archive (soft-delete) a storyline — reversible via storyline_restore |
storyline_restore |
Restore an archived storyline back to active state |
storyline_clarify |
Run the intake/clarification step (iterative Q&A until system has enough context) |
storyline_generate_brief |
Async: generate the marketing brief — positioning, key messages, audience, timing (poll via get_job) |
storyline_set_brief |
Manually set (replace) the full brief for a storyline |
storyline_edit_brief |
AI-edit the brief using natural-language instructions |
storyline_confirm_brief |
Confirm the brief and gate strategy generation |
storyline_get_strategy |
Fetch the generated strategy and its line items |
storyline_generate_strategy |
Async: generate the execution strategy and line item set (poll via get_job) |
storyline_edit_strategy |
AI-edit the strategy using natural-language instructions |
storyline_estimate |
Dry-run credit estimate for executing the storyline |
storyline_add_line_item |
Add a new content line item to the strategy |
storyline_update_line_item |
Edit an existing line item (channel, type, title, selected flag, etc.) |
storyline_delete_line_item |
Permanently remove a line item from the strategy (confirm: true required) |
storyline_regenerate_line_item |
Async: regenerate a single strategy line item (poll via get_job) |
storyline_execute |
Async: generate all selected drafts from the strategy (poll via get_job) |
Competitors (intelligence)
Canonical flow: competitor_probe → competitor_probe_status → competitor_probe_classify → competitor_add (poll) → competitor_analyze (poll) → competitor_list → competitor_get_comparison/recompute → competitor_get_overview/generate_overview (poll). Namespace: competitor_* (distinct from seo_competitor/seo_gap).
| Tool | Description |
|---|---|
competitor_list |
List tracked competitors with status, analysis state, and a dashboard deep-link |
competitor_add |
Async: batch-add 1–20 competitor domains and trigger crawl + profile analysis (poll via get_job) |
competitor_update |
Update competitor settings — e.g. toggle excludeFromSeoPull |
competitor_delete |
Soft-delete a tracked competitor (restorable via competitor_update with empty body) |
competitor_analyze |
Async: re-analyze pending or failed competitor rows (poll via get_job) |
competitor_refresh |
Async: refresh all active competitors — re-crawl + re-profile (poll via get_job) |
competitor_get_comparison |
Get the brand's head-to-head competitive comparison |
competitor_recompute_comparison |
Trigger a fresh comparison recompute (call after adding/analyzing competitors) |
competitor_get_overview |
Get the saved competitive landscape overview |
competitor_generate_overview |
Async: generate a fresh AI-synthesized landscape overview (poll via get_job) |
competitor_comparison_sources |
List SEO keyword sources that feed the competitive comparison |
competitor_probe |
Async: discover and surface rival domain candidates based on the brand (poll via get_job) |
competitor_probe_status |
Check the status of a probe run and list discovered candidates |
competitor_probe_classify |
Classify a probe candidate as add, skip, or blacklist |
Knowledge base
Canonical flow: knowledge_list → knowledge_get → knowledge_create (poll get_job) → knowledge_update → knowledge_delete.
| Tool | Description |
|---|---|
knowledge_list |
List knowledge base items — filter by tag, active status, or global flag |
knowledge_create |
Async: create a knowledge base item with optional AI enrichment (poll via get_job) |
knowledge_get |
Fetch a single knowledge base item with full content and metadata |
knowledge_update |
Update a knowledge base item's name, description, content, or tags |
knowledge_delete |
Soft-delete a knowledge base item |
PostKing MCP questions
How do I add PostKing MCP to Claude Code?
Run claude mcp add postking-mcp -- npx -y postking-mcp in your terminal. Add --scope user to make it available in every project.
How do I add PostKing MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does PostKing MCP provide?
It exposes 220 tools, including login_start, login_complete, logout, whoami, list_brands.
Do I need an API key to use this server?
No, PostKing uses a device login flow instead of requiring you to copy and paste API keys.
Can I repurpose existing content?
Yes, you can turn URLs, text, or existing posts into new social media or blog content using the repurpose tool.
What platforms can I publish blogs to?
The server allows you to push blog articles to platforms such as WordPress, Medium, and Substack.