Skip to main content
Glama
Sign In
Community Archive Connector

Community Archive Connector

by leo-guinan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Community Archive Connector

No user-submitted related servers found.

    Related Servers

    • twscrape-twitter-mcp

      jsilets
      A
      license
      A
      quality
      B
      maintenance
      MCP server to read X (Twitter) posts, threads, replies, quotes, and search using your own logged-in session, no API key required.
      8
      25 PyPI
      3
      MIT

    • x-mcp

      mc-nekoneko
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for public X/Twitter search and retrieval via twitter.2-38.com
      -

    • fanfou-mcp

      Anthonyeef
      A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients such as Claude and Cursor to read timelines, search statuses, and look up users or conversations, plus optionally post, delete, favorite, and follow with explicit confirmation. It supports both local stdio launches and remote HTTP hosting with per-user authorization.
      15
      MIT

    • twitterapis

      TwitterAPIs
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the Twitter/X API, enabling search, user profiles, tweets, followers, and more via natural language.
      94
      464 npm
      5
      MIT

    • social-reader

      duplonicus
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A local read-only MCP server that lets MCP clients such as the Claude app fetch X/Twitter posts and search, Reddit posts, threads and search, and YouTube transcripts and search. It reads through your own saved logins using a fixed set of read-only commands, and cannot post, vote, follow or message.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools occupy clearly distinct slots: fetch-by-ID (ca_get_tweets), full-text search (ca_search_tweets), per-account timeline (ca_account_tweets), and global date window (ca_tweets_window) are well separated by their descriptions. The riskiest cluster is identity lookup — ca_account vs ca_members vs ca_find_people — where an agent must pick between exact profile, member roster, and fuzzy name search, but the descriptions do state the distinctions.

    Naming Consistency4/5

    Every tool shares the ca_ namespace prefix and snake_case, which keeps the set readable as a unit. Verb style is mixed, though: some are verb_noun (ca_get_tweets, ca_search_tweets, ca_find_people), others are bare nouns (ca_account, ca_members, ca_receipt, ca_thread), and a few are phrasal (ca_first_said, ca_who_talks_about, ca_me).

    Tool Count5/5

    At 15 tools the set sits at the top of the well-scoped range, and each tool maps to a distinguishable query pattern (ID lookup, search, timeline, aggregation, relation graph) rather than duplicating another. Nothing appears redundant or padded.

    Completeness4/5

    The surface covers the read-only archive domain thoroughly: profiles, tweet retrieval by ID, search, per-account and global timelines, relations, threads, provenance receipts, and analytic queries (first use, phrase trends, topic experts, follow-graph overlap). Minor gaps remain — no aggregate account statistics (tweet/media counts) and no media or URL-entity listing — but these are workarounds rather than dead ends for a read-only connector.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources