FetchLayer fetchlayer.dev Get started

Integration Guide

· Updated August 29, 2026

Twitter/X MCP Server for AI Agents

FetchLayer's Twitter/X MCP server works with Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, and more. Pick your tool and connect in under a minute.

Written by Alex P.

  • MCP
  • twitter scraping
  • AI agent
  • Model Context Protocol

FetchLayer runs a single Model Context Protocol (MCP) server at https://mcp.fetchlayer.dev that exposes 10 Twitter/X tools — search, tweet and reply lookups, profile data, and follower graphs — to any MCP-compatible AI agent. The server is identical no matter which client you connect it to; only the config file location and restart step change per tool.

This page is the index for all of it. Pick your tool below for a client-specific walkthrough, or read on for what the server can do and how to choose between clients.

Pick your client

ClientTypeSetupGuide
Claude DesktopDesktop appEdit claude_desktop_config.jsonConnect Twitter MCP to Claude Desktop →
Claude CodeTerminal / CLIclaude mcp add or manual configSearch Twitter/X from Claude Code →
CursorAI code editorEdit mcp.json (global or per-project)Connect Twitter MCP to Cursor →
WindsurfAI code editorMCP settings panel or mcp.jsonConnect Twitter MCP to Windsurf →
VS Code (Copilot)Code editor.vscode/mcp.jsonConnect Twitter MCP to VS Code →
Hermes AgentAgent frameworkConfig fileConnect Twitter MCP to Hermes →
KiloCodeVS Code extensionExtension MCP settingsConnect Twitter MCP to KiloCode →
OpenClawAgent frameworkConfig fileConnect Twitter MCP to OpenClaw →

Every guide uses the same server URL (https://mcp.fetchlayer.dev) and the same Authorization: Bearer ss-your-api-key header — only where that block goes changes between tools.

Which one should you use?

  • Already coding in an AI-native editor? Cursor, Windsurf, and VS Code’s Copilot agent mode all support MCP natively — use whichever one’s already open. Setup is a JSON file edit and a reload.
  • Working conversationally, not in code? Claude Desktop is the fastest path — a config file and a restart, no terminal.
  • Live in the terminal? Claude Code adds MCP servers via a single CLI command.
  • Building your own agent on Hermes or OpenClaw? Both take the same server URL and header — the framework-specific config shape is in the guides above.
  • Running KiloCode inside VS Code? Use the KiloCode-specific guide — it reads its own MCP settings, not .vscode/mcp.json.

What the server can do

All 8 clients connect to the same 10 tools: twitter_search, twitter_tweet_detail, twitter_tweet_replies, twitter_user_profile_details, twitter_about_profile, twitter_user_tweets, twitter_user_replies, twitter_following, twitter_followers, and twitter_verified_followers. That covers keyword search, full tweet and reply lookups, profile and extended-metadata retrieval, and both sides of the follower graph — all as structured JSON, with no X Developer Portal application or OAuth flow required.

Get an API key

Every client needs a FetchLayer API key. Get one free — no credit card required — then follow the guide for your tool above.

Common issues across all clients

  • Tools not showing up? Check the config file path for your OS/tool, validate the JSON (no trailing commas), and fully restart the app rather than just reloading a window.
  • “Invalid API key” errors? Confirm the key starts with ss- and was copied in full from the FetchLayer dashboard.
  • Need REST instead of MCP? See the Twitter/X API reference for direct HTTP access to all 10 endpoints — the REST and MCP surfaces are 1:1 here.

What’s Next