Twitter/X Search API & MCP Server for AI Agents & Social Tools

The Press Monitor Advanced Twitter/X Search API provides programmatic access to search, tweet lookup, user profiles, and network graph endpoints (followers, followings), with pagination cursors and enterprise-ready JSON. Ideal for brand monitoring, influencer discovery, social listening, and AI/analytics pipelines.

---

Base Endpoint:

<https://api.pressmonitor.com/x/v1>

OpenAPI Schema: Download Schema 

---

All endpoints require Bearer Token authentication:

Authorization: Bearer YOUR_TOKEN

Each request deducts credits based on content type. Credits and request IDs are returned in responses for usage tracking.

• GET /search — advanced search across Tweets, Photos/Media, People, Latest, and Lists
• GET /tweet — retrieve a Tweet by ID (rich engagement + media)
• GET /user — lookup a user by username
• GET /followers — followers of a user (paginated)
• GET /followings — accounts a user follows (paginated)
• GET /user-tweets — recent tweets by a user (paginated)
• GET /get-users — bulk lookup by user IDs (comma-separated)
• GET /verified-followers — only verified followers (paginated)

---

/search

• query (required) — search term/keyword
• type (required) — Top | Photos | Media | People | Latest | Lists
• count (optional) — page size (endpoint max applies)
• cursor (optional) — pagination cursor from previous page

/tweet

• pid (required) — tweet ID

/user

• username (required) — screen name without @

/followers, /followings, /user-tweets, /verified-followers

• user (required) — target user ID (rest_id)
• count (optional) — page size
• cursor (optional) — pagination

/get-users

• users (required) — comma-separated user IDs

---

Most list endpoints return an array of objects. Pagination support is provided via a cursor parameter (request) and may be surfaced as next_cursor in responses.

---

Search (Latest)

curl -s "https://api.pressmonitor.com/x/v1/search?query=AI%20models&type=Top&count=20" -H "Authorization: Bearer YOUR_TOKEN"

Tweet by ID

curl -s "https://api.pressmonitor.com/x/v1/tweet?pid=1964395588927000801" -H "Authorization: Bearer YOUR_TOKEN"

Followers (paginated)

curl -s "https://api.pressmonitor.com/x/v1/followers?user=2455740283&count=50&cursor=NEXT_CURSOR" -H "Authorization: Bearer YOUR_TOKEN"

Bulk Users

curl -s "<https://api.pressmonitor.com/x/v1/get-users?users=44196397>,2455740283" -H "Authorization: Bearer YOUR_TOKEN"

---

• Use cursor to page large result sets efficiently.
• Respect endpoint count maximums to avoid throttling.
• Cache non-volatile lookups (e.g., user profile by ID).
• Log request_id (if present) for support/usage tracing.

---

Docs & Guides: https://www.pressmonitor.com/en/docs/twitter-x-api  Email: support@pressmonitor.com 

The Press Monitor X MCP Server exposes Twitter/X tools over JSON-RPC 2.0 for AI agents and automations. All tool names map 1:1 to the API operationIds, with structured output that includes a data envelope (items + pagination) and credits for metering.

---

Base Endpoint:

<https://mcp.pressmonitor.com/x/v1>

OpenAPI Schema: Download Schema 

---

All endpoints require Bearer Token authentication:

Authorization: Bearer YOUR_TOKEN

Each request deducts credits based on content type. Credits and request IDs are returned in responses for usage tracking.

---

List the available tools via JSON-RPC:

curl -s -X POST "https://mcp.pressmonitor.com/x/v1" -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Common tools (operationId = tool name): search, tweet, user, followers, followings, userTweets, getUsers, verifiedFollowers.

---

curl -s -X POST "https://mcp.pressmonitor.com/x/v1" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_TOKEN" -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "search", "arguments": { "query": "AI safety", "type": "Top", "count": "25" } } }'

Expected output envelope:

{ "jsonrpc": "2.0", "id": 1, "result": { "content": [{ "type": "json", "json": { "data": { "items": [ /* array of tweets/users/media depending on type */ ], "next_cursor": "string or null" }, "credits": { "rate": 1, "quantity": 1, "total": 1, "request_id": "..." } } }] } }

---

curl -s -X POST "https://mcp.pressmonitor.com/x/v1" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_TOKEN" -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "followers", "arguments": { "user": "44196397", "count": "50" } } }'

---

{ "mcpServers": { "pressmonitor-x": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.pressmonitor.com/x/v1", "--header", "Authorization: Bearer ${X_API_TOKEN}" ], "env": { "X_API_TOKEN": "" } } } }

---

• Keep count reasonable (e.g., 25–100) and always reuse next_cursor for pagination.
• Tool outputs follow the declared outputSchema with data.items and data.next_cursor plus credits.
• For reproducible analytics, store request/response pairs with timestamps and request IDs.

---

Docs & Guides: https://www.pressmonitor.com/en/docs/twitter-x-api  Email: support@pressmonitor.com