X MCP Server

Created By
siddheshutda year ago
This is an MCP server for the X Platform
Overview

What is X MCP Server?

X MCP Server is a tool designed for interacting with the X platform through various MCP clients such as Claude, Cursor AI, and Windsurf AI.

How to use X MCP Server?

To use X MCP Server, clone the repository, install the dependencies, build the project, and configure it with your X Developer API keys. Then, set up the MCP server in your preferred client.

Key features of X MCP Server?

  • Interacts with the X platform via multiple MCP clients.
  • Supports configuration for different clients like Claude, Cursor AI, and Windsurf AI.
  • Built with Node.js and TypeScript for efficient performance.

Use cases of X MCP Server?

  1. Connecting AI clients to the X platform for data retrieval.
  2. Facilitating communication between MCP clients and the X platform.
  3. Enabling developers to create custom integrations with the X platform.

FAQ from X MCP Server?

  • What are the prerequisites for using X MCP Server?

You need Node.js (>=18.0.0), npm (>=8.0.0), and X Developer API keys.

  • How do I configure the server for different clients?

Follow the specific instructions provided for each client in the documentation.

  • Is there a rate limit for using the X APIs?

Yes, there is a rate limit set by the X platform, which can be checked on their developer portal.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
siddheshutd
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 days ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago