Alidade MCP
OfficialRelated Servers
Alternatives to Alidade MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceMCP server for the official X API, enabling agents to read and publish posts, look up users, and search posts with safe read-only default and explicit write mode.817 npm-
- AlicenseNot gradedqualityBmaintenanceThis MCP server lets an assistant operate your own X account — posting, threads, media, timelines, search, DMs, bookmarks, lists, trends, analytics, and profile actions — exposing one tool per operation plus meta-tools for schema search and validated invocation. It uses the official X API for 49 operations and keeps 11 unofficial browser-session actions such as likes, follows, and profile edits off by default, available only after explicit opt-in with cookies and a risk acknowledgment.Apache 2.0
- AlicenseAqualityCmaintenanceAn MCP server that provides AI agents with full access to the X (Twitter) API for posting, searching, and managing engagement through natural language. It supports comprehensive tools for tweet management, media uploads, and account analytics across multiple MCP-compatible clients.1563MIT
- AlicenseNot gradedqualityBmaintenanceProvides a single MCP endpoint that dynamically discovers, routes, policy-checks, and executes hundreds of MCP tools from any agent, with optional LLM-based routing.19 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables LLM agents to access multiple stdio or Streamable HTTP MCP servers through one authenticated endpoint, enforcing OAuth bearer validation, per-client tool RBAC, rate limits, schema validation, audit logging, and tool-definition pinning.MIT

X API FastMCP Serverofficial
FlicenseNot gradedqualityDmaintenanceA local MCP server that exposes the X API (formerly Twitter API) as tools, enabling operations like posting, searching, user management, and more via natural language commands.870-
TDQS
Scored across 13 tools
Every tool targets a distinct resource+action, and the two potentially confusable tools (search_mentions vs semantic_search_mentions) are explicitly contrasted in their descriptions as chronological/label-filtered vs pure vector similarity. Similarly find_entities, get_entity, and list_organizations have clearly separated roles, and the saved-search CRUD tools are unmistakable.
Almost all tools follow a predictable snake_case verb_noun pattern (get_analytics, create_saved_search, delete_saved_search, list_organizations). The only deviation is semantic_search_mentions, which prefixes a modifier before the verb, and the mix of find_/list_ for discovery verbs is slightly inconsistent though still readable.
13 tools is squarely in the well-scoped range, with each tool earning its place: discovery (list/get saved searches, organizations, entities), querying (mentions, semantic mentions, ads, analytics), and lifecycle management (create/update/delete saved search). No obvious redundancy or padding.
Saved-search lifecycle is fully covered (list/get/create/update/delete), and the analytics surface spans mentions, ads, entities, and multiple metrics. Minor gaps exist around app-only concepts referenced in descriptions (bulletins, readouts, chat projects, dynamic group creation) that have no API tools, but agents can work around these.