FetchLayer fetchlayer.dev Sign in

+ Integration Guide

How to Connect Twitter MCP to Claude Desktop

Add FetchLayer's Twitter/X MCP server to Claude Desktop so Claude can search tweets, get profiles, and pull follower data in your conversations.

Written by Alex P.

  • MCP
  • Claude Desktop
  • twitter scraping
  • X scraping
  • AI agent
  • Anthropic

Claude Desktop is Anthropic’s native desktop app for Claude. It supports the Model Context Protocol (MCP), which lets Claude call external tools — including Twitter/X data from FetchLayer.

Once configured, you can ask Claude to search tweets, analyze profiles, pull follower graphs, and more — all inside a normal conversation.


Prerequisites


Step 1: Open the Claude Desktop config

Claude Desktop reads MCP server configurations from a JSON config file. The location depends on your OS:

macOS:

~/Library/Application Support/Claude/claude_desktop_config.json

Windows:

%APPDATA%\Claude\claude_desktop_config.json

Linux:

~/.config/Claude/claude_desktop_config.json

If the file doesn’t exist, create it. You can also open it from Claude Desktop: go to Settings → Developer → Edit Config.


Step 2: Add the FetchLayer MCP server

Add this configuration to your claude_desktop_config.json:

{
  "mcpServers": {
    "fetchlayer": {
      "url": "https://mcp.fetchlayer.dev",
      "headers": {
        "Authorization": "Bearer sk-your-api-key"
      }
    }
  }
}

Replace sk-your-api-key with your actual API key from the FetchLayer dashboard.

If you already have other MCP servers, add "fetchlayer" next to them:

{
  "mcpServers": {
    "filesystem": { "command": "..." },
    "fetchlayer": {
      "url": "https://mcp.fetchlayer.dev",
      "headers": {
        "Authorization": "Bearer sk-your-api-key"
      }
    }
  }
}

Step 3: Restart Claude Desktop

Quit Claude Desktop completely and reopen it. The app loads MCP configs on startup.

You should see a small hammer/tools icon in the chat input area — this indicates MCP tools are available. Click it to see “fetchlayer” listed with all its Twitter tools.


Step 4: Try it out

Start a new conversation and try:

Search X/Twitter for posts about “best project management tools” from the last month. Show me the top 5 with engagement stats.

Claude will call the FetchLayer search tool and return structured results.

More ideas:

PromptWhat Claude does
”What’s @levelsio tweeting about lately?”Fetches recent user tweets
”Summarize the replies to this tweet: [URL]“Pulls replies, then summarizes
”Find verified accounts following @openai”Returns verified followers list
”What’s the sentiment about AI coding tools on X/Twitter right now?”Searches, reads tweets, analyzes tone
”Get me the profile for @rauchg”Returns user profile data

Because Claude can chain tool calls with reasoning, it can do multi-step analysis — search for tweets, pull profiles, compare follower counts, and synthesize findings in one conversation turn.


Available Tools

Claude Desktop gets access to all FetchLayer Twitter/X tools:

  • twitter_search — Search tweets by keyword
  • twitter_tweet_detail — Get a specific tweet by ID
  • twitter_tweet_replies — Fetch replies to a tweet
  • twitter_user_profile_details — Get user profile by handle
  • twitter_about_profile — Extended profile metadata
  • twitter_user_tweets — A user’s recent tweets
  • twitter_user_replies — A user’s recent replies
  • twitter_following — Accounts a user follows
  • twitter_followers — Accounts following a user
  • twitter_verified_followers — Verified accounts following a user

Troubleshooting

Tools icon not showing?

  • Make sure the config file path is correct for your OS
  • Validate the JSON (no trailing commas, proper quoting)
  • Fully quit and relaunch Claude Desktop (not just close the window)

Claude says it can’t access Twitter?

  • Check that your API key is valid
  • Make sure you’re in a new conversation (MCP tools aren’t available in old chats started before config change)

Getting errors in tool calls?

  • Look at the tool call details in Claude’s response — it shows the error message
  • Most common: invalid API key or malformed request body

What’s Next