v1.0.4 — README polish: roadmap refresh, Discord invite fix, SDK links

Docs-only. See PR #4 for the full changeset.

v1.0.3 — README: list all 47 tools + honest about aggregation limits

Docs-only release. No behavior changes, no schema changes — same 47 tools as v1.0.2. The bump exists so the npm-displayed README updates for customers discovering the package.

What's in the README now

Full tool list (was 12, now 47)

Previous README listed Facebook Pages (4) + Groups (3) + Posts (5) = 12 tools and said "More platforms coming soon: Instagram, TikTok, YouTube, Twitter". Instagram was already fully implemented (16 tools), and the Facebook surface also includes Search (5), Ads Library (5), Marketplace (7), and Media (1). 35 tools were undocumented.

New README lists all 47 tools across 10 categories with one-line descriptions + pricing-affecting params (e.g. exact_followers_count charging 5 credits) flagged inline.

Honest "Coming soon" footer

TikTok / X (Twitter) / LinkedIn / YouTube — matches the actual platform roadmap.

Usage examples — single-call vs multi-call

Old examples mixed cheap-single-call patterns ("Monitor Nike's page") with hard-multi-call patterns ("Compare engagement over the last month") without flagging the difference. New section splits into:

• Single-call patterns (fast, cheap) with credit cost noted per example
• Multi-call patterns — explicit about Claude orchestrating N calls + the cost implication

New "What this MCP server does NOT do" section

Four real limitations, named honestly:

Query shape	Why it's hard
"Engagement rate over the last 30 days" for a page	Paginated fetch + per-post aggregation — hits the LLM tool-call budget on busy pages
"Compare engagement rates between A, B, C over the last month"	Same problem, 3×
Historical archive older than what Facebook itself serves	We surface what Facebook makes publicly visible
Server-side time-series (daily / weekly metrics)	Roadmap item — engagement-stats endpoint with built-in aggregation

Closes with: "If your use case maps to one of these patterns and you want the aggregation pre-computed, contact support — we're prioritizing the aggregation endpoint based on customer demand."

Upgrade

npm install @socialapis/mcp@latest
# or in your Claude Desktop / Cursor config:
"args": ["-y", "@socialapis/mcp@1.0.3"]

Full PR

#3

v1.0.2 — fix /v1 URL bug + new tool params

Fix the production-blocking URL bug

v1.0.1 (published 2025-12-18) defaulted API_BASE_URL to https://api.socialapis.io/v1. The real public API has no /v1 prefix on /facebook/* and /instagram/* endpoints — they live at the root. Every npm-installed MCP customer on v1.0.1 had been getting 404s on every tool call since the publish.

If you installed @socialapis/mcp@1.0.1, please upgrade to v1.0.2.

npm install @socialapis/mcp@latest
# or, in your Claude Desktop / Cursor config:
"args": ["-y", "@socialapis/mcp@1.0.2"]

New tool parameters

Tool input schemas now expose the new query params shipped in the public REST API:

• facebook_get_page_details — new exact_followers_count (boolean). When true, the API performs a deeper scrape and returns the exact integer follower count (e.g. 38,493,217) instead of the rounded display value ("38M"). Charges 5 credits when true, 1 otherwise.
• facebook_get_page_posts — new limit (number, default 3, min 3, max 9). Charges scale per ceil(posts_returned / 3).
• facebook_get_group_posts — same limit constraint + scaled pricing.
• facebook_get_page_videos — new limit (number, default 6, min 6, max 12).
• facebook_get_post_comments — new limit (number, default 10, max 30).
• facebook_marketplace_search — new limit (number, default 24).
• facebook_get_post_attachments — description now flags 5-credit pricing.

JSON Schema minimum / maximum constraints on the numeric limit fields so MCP clients (Claude Desktop, Cursor, etc.) surface the bounds at parameter-edit time.

Sanity check

47 unique tools registered, 0 duplicates, 0 broken required references (every name in a tool's required array is defined in its properties).

Full PR

#2