Model Context Protocol
One MCP server.
Six platforms of data.
Connect Claude, Cursor, Windsurf, or any MCP-compatible agent to Reddit, Twitter/X, App Store, Google Play, YouTube, and Google Maps data — live, structured, and callable mid-conversation. No wrapper code, no separate server per platform.
MCP & agents
Your AI already knows
how to use this.
One config block and every endpoint across all six platforms becomes a first-class tool inside your agent. No SDK, no wrapper code, no glue logic — just paste and go.
Pick your editor and we hand you the config with your key already in it — no JSON to hand-edit, no wrapper code.
Get your free API keyFree tier · no credit card · any MCP host
Search Reddit and pull the latest App Store reviews for "Superhuman" — summarize what people are complaining about this week.
Found 6 Reddit threads and 14 App Store reviews. The recurring complaint on both is sync delay after the 4.2 update — cited in 9 of the 14 reviews and 4 of the 6 threads...
Works with every MCP-compatible tool
Pick your platform
Every platform, one connection.
Each platform has its own set of MCP tools and a dedicated setup guide. The server connection is the same one you already made above — these just cover what's available once you're connected.
13 MCP tools
Twitter / X
11 MCP tools
App Store & Play Store
8 MCP tools
YouTube
6 MCP tools
Google Maps
5 MCP tools
FAQ
Questions about the MCP server.
What is the FetchLayer MCP server?
It's a Model Context Protocol server at https://mcp.fetchlayer.dev that exposes FetchLayer's Reddit, Twitter/X, App Store, Google Play, YouTube, and Google Maps tools directly to your AI agent or IDE. Instead of writing wrapper code that calls our REST API and parses the response, your agent calls the tool directly — search Reddit, pull App Store reviews, scrape a YouTube video's comments — and gets structured JSON back inline, in the same conversation.
Which AI tools does it work with?
Any MCP-compatible client: Claude Desktop, Claude Code, Cursor, Windsurf, VS Code (via an MCP-compatible extension), Hermes, Kilocode, and OpenClaw are all supported today, with setup guides for each. If your tool speaks MCP over stdio or HTTP, it can connect — the protocol is the same regardless of client, only the config file location and format change.
Does the MCP server cost extra?
No. MCP calls draw from the same API credits as direct REST calls — one tool call is one request, at the same $1.99 per 1,000 requests pay-as-you-go rate, or covered by your subscription plan if you have one. There is no separate MCP tier, no markup, and no additional key to manage: the same Bearer token that authenticates your REST calls authenticates your MCP connection.
Is one server really enough for six platforms?
Yes. Rather than shipping a separate MCP server per platform, FetchLayer runs a single server that exposes every platform's tools together, namespaced by platform (fetchlayer.reddit.search, fetchlayer.youtube.comments, and so on). You connect it once and your agent has access to whichever platforms your plan includes — no juggling multiple server URLs or config blocks as you add platforms.
What can my agent actually do with it?
Anything the REST API can do: search and read Reddit posts and comments, pull a subreddit's feed, fetch public App Store or Google Play reviews for an app, extract YouTube video comments and transcripts, look up Google Maps reviews for a business, and more — all as callable tools your agent invokes mid-conversation instead of you copy-pasting API responses in by hand.
Do I need to write any code to set it up?
No. Setup is a config block — your API key and the server URL, pasted into whichever file your client uses for MCP servers. Each client-specific guide below has the exact file path and a copy-paste config. There's no SDK to install and no server to run yourself; the server is hosted and maintained by FetchLayer.
Can I use it alongside the REST API?
Yes, freely — they're the same underlying service. Use the REST API from your backend for scheduled jobs or pipelines, and the MCP server from your IDE or agent for interactive, conversational lookups. Same API key, same usage counted against the same plan.
Pricing
Start free. Scale when ready.
Pay per request with no commitment, or lock in a flat monthly rate with built-in savings.
Free plan — 30 requests
Verify responses, inspect the API, no credit card required.
Pay as you go
$1.99
per 1,000 requests
$0.00199 per request · credits never expire
How credits work — no multipliers
One credit = one API call, on every endpoint and platform. No matter how many results come back, you pay for the call, not the output size. Most scraping APIs charge multipliers of 5x, 25x, even 75x per call depending on the target — here it's always 1.
- No multipliers — 1 request = 1 credit
- No monthly commitment
- Credits never expire
- Same API & MCP access as subscribers
- ∞ req/min, ∞ API keys
∞
Expiry
Credits stay until you use them. No monthly reset, no pressure to hit a quota.
0
Commitments
No subscription, no contract, no minimums. Start, pause, or scale whenever.
100%
Access
Every endpoint and MCP included. Not a limited tier — same data as any subscriber.
Used by developers at
Individual developers or teams — not official partnerships