Skip to main content
Glama
jackleeio

bnbot-mcp-server

by jackleeio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to bnbot-mcp-server

No user-submitted related servers found.

    Related Servers

    • X MCP Server

      siddheshutd
      A
      license
      B
      quality
      D
      maintenance
      MCP server for interacting with the X platform (Twitter) via MCP clients like Claude, Cursor AI, and Windsurf AI.
      20
      5 npm
      6
      MIT

    • x-mcp-playwright

      Steph-ux
      A
      license
      Not graded
      quality
      B
      maintenance
      A Twitter/X MCP server powered by patchright (stealth Playwright fork) and a persistent Chrome user profile. It enables posting, engaging, searching, and managing tweets, threads, media, and user interactions via natural language.
      1
      MIT

    • X(Twitter) V2 MCP Server

      NexusX-MCP
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with the Twitter/X API v2, enabling AI assistants to retrieve tweets, post content, reply, quote, and more programmatically.
      681 npm
      13
      MIT

    • twitterapi.mcp

      pedrot95dev
      A
      license
      A
      quality
      A
      maintenance
      MCP server that exposes twitterapi.io endpoints as tools for AI agents, enabling reading tweets, mentions, thread context, and writing tweets with cookie-based authentication.
      4
      13 npm
      MIT

    • twscrape-twitter-mcp

      jsilets
      A
      license
      A
      quality
      A
      maintenance
      MCP server to read X (Twitter) posts, threads, replies, quotes, and search using your own logged-in session, no API key required.
      8
      3
      MIT
    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

    B3.3/5.0

    Scored across 31 tools

    Disambiguation4/5

    Each tool largely targets a distinct action or resource (navigation, scraping, posting, engagement, article creation), and descriptions clarify boundaries. The only notable overlap is create_article duplicating the granular open_article_editor, fill_article_title, fill_article_body, upload_article_header_image, and publish_article tools, which could confuse an agent about which path to use.

    Naming Consistency4/5

    Predominantly consistent snake_case verb_noun pattern (e.g., post_tweet, scrape_timeline, navigate_to_tweet, fetch_wechat_article). Minor deviations exist: retweet lacks a noun, account_analytics has no verb, and return_to_timeline uses 'return' instead of 'navigate'. Still highly readable and mostly predictable.

    Tool Count2/5

    31 tools is above the typical 3-15 range, and the article workflow is unnecessarily split into six granular tools plus a redundant create_article wrapper. While the breadth of Twitter automation and cross-platform fetching justifies many tools, the count feels heavy and includes clear redundancy.

    Completeness4/5

    Core Twitter/X lifecycle is well covered: navigation, scraping, posting, replying, liking, retweeting, quoting, following, analytics, and long-form articles. Minor gaps exist (e.g., delete tweet, bookmark/unbookmark, direct messages, reading notifications), but agents can accomplish most stated goals.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources