PlanVortex

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/taliasoftworks-planvortex

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

22 read · 3 write · 7 delete

Secrets

1 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Node.js package

Tools (32)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• create_ai_planGenerate a week of posts with AIcan change or delete data

  Ask PlanVortex's AI to write a week of posts for one or more connected accounts. THIS SPENDS AI CREDITS and the user pays for them, so show them the estimate from get_planner_templates and get their agreement before calling it. It does NOT return posts: it queues the plan and returns the budget that was approved — poll get_ai_plan until the state is generated. What comes out are DRAFTS for a person to review, never anything published. The plan is weekly and its size is (publish_days x accounts), at most one post per day and account: three accounts on Monday, Wednesday and Friday is 9 posts, no…

• create_connect_linkCreate an account connection link

  Connecting a social account CANNOT be done by you: it is an OAuth flow with a person clicking 'authorize' on the network's own screen. This tool returns a single-use link that expires in fifteen minutes — give it to the user and ask them to open it in their browser. Do not claim an account is connected until list_accounts shows it.

• create_publicationCreate or schedule a postcan change or delete data

  Publish now or schedule a post on ONE connected account. Pass state 'ready' with a future publish_date to schedule, or 'draft' to leave it for a person to review. Media has to be uploaded first with upload_media; pass the returned ids in files. The text is validated against the network's limits before anything is sent. On Pinterest a pin needs things no other network asks for: a board (destination_id, from list_destinations), at least one image or video — a pin is never text alone — and, if it should lead somewhere, the URL in link. On TikTok the user has to choose who can see the post (visibi…

• get_account_metricsGet account metricsread-only

  Followers and how they moved over time for one connected account. Which series exist depends on the network, so ask for a range and read what comes back rather than assuming a metric is there.

• get_ai_planGet one AI planread-only

  One plan with its state, what it has spent, and the posts it generated. This is what you poll after create_ai_plan: while the state is pending or generating nothing exists yet, and generation can take minutes. Once it is generated, the posts are ORDINARY publications in draft state — read them with get_publication and edit or schedule them with update_publication, not with anything here. A failed plan carries the reason in error, and a generated one may still carry warnings worth reading out.

• get_ai_plan_resultsCompare the results of AI plansread-only

  Which AI plans worked, and which template works best — the tool for 'which of my AI plans did best?'. Each plan comes with what its published posts achieved, plus an aggregate per template. Plans are ranked by interactions per MEASURED post, not by the total (the total just rewards bigger plans), and only plans marked ranked (at least 3 measured posts) compete; maturing means its numbers are still moving, so say so before comparing it with an older plan. The range filters on the week the plan published in. To compare plans fairly across networks, pass one social_network. Missing metrics are no…

• get_comment_threadRead a comment thread liveread-only

  Read a thread straight from the social network, reconciled with what PlanVortex stored — the network wins. Pass id_publication for a post, or id_account for a Google Business listing, whose reviews hang off the listing and not off any post. On X this costs one credit per reply returned. Telegram has no live read: its comments only exist in the PlanVortex inbox, so use list_comments there. Slack and Pinterest have no comment inbox at all — a Slack thread is not read by PlanVortex, and Pinterest does not expose a pin's comments — so do not try, and do not retry: it is not a temporary failure. Ne…

• get_dashboard_summaryGet dashboard summaryread-only

  The aggregate for a date range: totals by network, plan usage, unread messages, accounts in error and posts that failed. This is the one call for 'how did this month go?' — prefer it over stitching several tools together.

• get_plan_useGet plan usageread-only

  What the organization's plan allows and what it has already used: accounts, storage and integrations. Check this before promising the user a connected account — a plan limit is not a transient error and retrying never fixes it. PUBLICATIONS ARE UNLIMITED on every plan: the count is reported for context and has no ceiling, so never refuse to schedule posts over it. What can stop a batch is rate — a per-hour cap per account and a daily cap per network, both in get_social_limits — and that one IS transient: waiting fixes it.

• get_planner_templatesGet the AI planner templatesread-only

  Description is built at runtime.

• get_publicationGet one publicationread-only

  The full record of one post, including publication_errors — the list of reasons it did not go out. This is the tool to call when the user asks why a post failed.

• get_publication_statsGet one post's statsread-only

  The measurements of a single post over time. Each point is the CUMULATIVE value at that date, not that day's increment. Keys a network does not measure are absent, never zero.

• get_social_capabilitiesGet per-network capabilitiesread-only

  What each network can actually do — publish, private messages, comments, products, webhooks — plus the comment moderation matrix: whether a reply, a hide or a delete is possible there. Not every network does everything: WhatsApp has no wall, Google Business does not publish at all, LinkedIn cannot hide a comment, and Slack and Pinterest publish but have no comments to read. Two columns are about publishing: destinations means every post needs a place inside the account (Pinterest's board, see list_destinations), and link means the post carries a destination URL of its own. visibility, interact…

• get_social_limitsGet per-network limitsread-only

  The hard limits of every network: characters, post bytes, title length, number of images, video duration and file size. Check these before writing a post — the same text is fine on LinkedIn and rejected on X. Two of them are not interchangeable: Bluesky counts BOTH 300 characters and 3000 bytes, and an emoji is one character but several bytes.

• get_top_publicationsGet best performing postsread-only

  The best performing posts of a range, ranked by one metric. This is the tool for 'what worked?'. Networks measure different things, so a ranking by impressions silently leaves out the networks that have none — rank by engagement to compare across all of them.

Signals

Stars

0

Forks

0

Open issues

0

Last commit

Oct 23, 2026 (8 days ago)

Last release

Oct 20, 2026 (10 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.taliasoftworks/planvortex

Version

0.13.0

Auth

API key

Packages

npm planvortex-mcp

License

MIT

Repository

github.com/taliasoftworks/PlanVortexMCP

Website

planvortex.com/en/developers

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql