Postlint MCP Server vs SocialCrawl

A side-by-side look at the Postlint MCP Server and SocialCrawl MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Postlint MCP Server logoPostlint MCP ServerSocial Media · Local subprocess (stdio)Check a social post against a platform's real character limit: X, Bluesky, LinkedIn, Threads.60GoodAuth: not declaredSocialCrawl logoSocialCrawlSocial Media · Local subprocess (stdio)Access 21+ social media platforms through one unified API. Profiles, posts, search.56GoodAuth: not declared

Verdict: choose Postlint MCP Server for social media work as a local process; choose SocialCrawl for social media as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Postlint MCP Server logoChoose Postlint MCP Server when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like check_post, check_post_all, platform_limits.
Explore Postlint MCP Server

SocialCrawl logoChoose SocialCrawl when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: SOCIALCRAWL_API_KEY.
  • You want tools like socialcrawl_find, socialcrawl_endpoint, socialcrawl_estimate.
Explore SocialCrawl

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPostlint MCP Server logoPostlint MCP ServerSocialCrawl logoSocialCrawl
CategorySocial MediaSocial Media
Quality signal60/100 · Good56/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedSOCIALCRAWL_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools37

Tools & capabilities

Postlint MCP Server tools 3

  • check_postCheck a social post against one platform's real character limit and report whether it fits. Returns the counted length, the limit, and what drove the count (URLs billed at a fixed width, non-Latin characters billed double, emoji sequences collapsed to one grapheme). Use this before publishing anything with a hard limit — the counting rules are per-platform and are not text.length.
  • check_post_allCheck one post against every platform at once and get a row per platform: counted length, limit, and whether it fits. Use this when deciding where a draft can go as-is. The per-platform arithmetic is included only for the platforms it fails, to keep the response small — call check_post for a single platform's full breakdown.
  • platform_limitsList the platforms this server knows, with each one's limit, the unit it is measured in, why that unit is not a plain character count, and the source the number came from. Use it to explain a result or to see what is covered.

SocialCrawl tools 7

  • socialcrawl_findStart here: a task in plain words -> the best endpoints (3 by default) of 646, each with the params the task supplies (URLs and @handles resolved), the params still missing, the credit cost and the exact call. With no task it lists platforms, or one platform's endpoints. Free; no key needed.
  • socialcrawl_endpointRead before calling: one endpoint's purpose, params, where the rows are and up to 25 response fields, cost rule, paging, latency, timeout, next endpoints and a sample link. id (or platform+resource, path), a platform slug (its endpoints) or a guide topic. Free.
  • socialcrawl_estimateExact credits before you spend: one call (id, platform+resource or path, plus the params you will send; calls for a job total; items for a walk) or a plan of several calls. Uses the API's estimator when available, else the bundled pricing. A platform slug gives its price table; no id gives the pricing overview. Free.
  • socialcrawl_requestCall one endpoint (platform+resource, or id, or path). Validated locally first (a bad call is free), quoted, refused above max_credits and confirmed above the threshold. A large page is cut at row boundaries; socialcrawl_collect result_id reads the rest. Spends credits; needs SOCIALCRAWL_API_KEY.
  • socialcrawl_collectWalk a paged endpoint (id, platform+resource or path) to `items` unique rows, the last page or max_credits: cursors supplied, duplicates dropped, stops on a 402, refused free when one page exceeds max_credits. Small results come back whole. result_id (+offset, limit, format) reads a stored result, free. Spends credits.
  • socialcrawl_accountFree checks: balance (with this session's spend), transactions (itemised ledger; the receipts for one request_id), status (platform health; read it before retrying a 502/503) and freshness (whether this server's bundled catalogue is behind the API).
  • socialcrawl_manageStateful work by area + action: monitors (scheduled recipes, webhooks, alerts), cohorts (mention search over your own panel of accounts), web (scrape, search, crawl and agent jobs, change monitors, browser sessions) and jobs (Prism background jobs). A wrong field is refused free with the rules. Managing is free; scrapes, jobs, queries and monitor runs bill credits. dry_run: true validates and quotes a create/update and never creates it. rows_new alerts need track (id=monitors).

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Postlint MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "postlint-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@conorbronsdon/postlint-mcp"
      ]
    }
  }
}

SocialCrawl

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "socialcrawl": {
      "command": "npx",
      "args": [
        "-y",
        "socialcrawl-mcp"
      ],
      "env": {
        "SOCIALCRAWL_API_KEY": "YOUR_SOCIALCRAWL_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Postlint MCP Server is categorized under Social Media and uses a local stdio subprocess. SocialCrawl belongs to Social Media and uses a local stdio subprocess. Pick Postlint MCP Server for social media work and SocialCrawl for social media.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Postlint MCP Server has no declared pricing — check the project's own site. SocialCrawl has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add postlint-mcp-server and socialcrawl as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Postlint MCP Server has a quality signal of 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars. SocialCrawl has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.