anysiteio/anysite-mcp-server

**The entire web is your database. Your AI assistant is the query interface.**
A Model Context Protocol server that lets Claude, Cursor, ChatGPT, and any MCP client query structured data from LinkedIn, Instagram, Twitter/X, Reddit, YouTube, SEC EDGAR, Y Combinator, Crunchbase, and any URL on the web — through five universal tools, plus CRM write-back tools.
---
Quick start
Connect directly to the hosted server at https://mcp.anysite.io/mcp. It speaks MCP over Streamable HTTP with OAuth 2.0, and works with Claude Desktop, Claude Code, Cursor, Cline, Windsurf, ChatGPT, and any MCP-compliant client.
> **If your client supports HTTP transport, you do not need this npm package.** The package exists as a stdio bridge for clients that only speak stdio.
Step 1: Sign up
Create an account at anysite.io. The MCP30 promo covers your first month of MCP Unlimited ($30/month, 6 req/min fair-use, no credit counting). Credit-based plans (Starter $49 / Growth $200 / Scale $300 / Pro $549 / Enterprise from $1,199) also include MCP access; see docs.anysite.io/mcp-server/overview.
Step 2: Connect your client
Claude Desktop — OAuth
1. Settings → Connectors → Add Custom Connector
2. URL: https://mcp.anysite.io/mcp
3. Click Connect, authorize in the browser
4. **Required:** Settings → Capabilities → Tool access → **Tools already loaded**
The last step is critical. Claude Desktop's "Load tools when needed" mode uses name-based matching that fails on generic names like discover and execute. If you skip it, the tools exist but the model will not reliably call them.
Claude Code
The URL carries your API key — treat it as a secret.
Cursor
Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json in the project root:
Cline, Windsurf, ChatGPT, any MCP client
Point any compliant client at https://mcp.anysite.io/mcp and authenticate via OAuth or ?api_key=YOUR_KEY.
Step 3: Verify
Ask the assistant:
It should list: discover, execute, get_page, query_cache, export_data — plus eight crm_* tools if the CRM integration is enabled on your account.
Step 4: Run a query
The assistant runs discover on LinkedIn, picks the right search endpoint, calls execute, then narrows server-side with query_cache.
---
stdio bridge (npm package)
@anysiteio/mcp is a thin local proxy: it runs on stdio and forwards every request to https://mcp.anysite.io/mcp over Streamable HTTP with your token. No business logic lives in the package — tools, instructions, caching and exports all come from the server, so new endpoints and tools appear without a package update.
Use it when your client cannot speak HTTP transport: stdio-only IDE plugins, older Cline/Continue builds, custom stdio runners, or environments where outbound HTTP must go through a managed local process.
Install
Or run on demand with npx -y @anysiteio/mcp.
Configure your client
That is the entire configuration. Only ANYSITE_ACCESS_TOKEN is required — create one at app.anysite.io. The token can also live in ~/.anysite-mcp.env.
---
The tools
| Tool | Purpose |
|---|---|
| discover(source, category) | List endpoints in a category with their params and LLM hints. Always call before execute. |
| execute(source, category, endpoint, params) | Fetch data. Returns first 10 items + cache_key. |
| get_page(cache_key, offset, limit) | Paginate cached items without re-fetching (limit ≤ 50). |
| query_cache(cache_key, conditions?, sort_by?, aggregate?, group_by?) | Filter / sort / aggregate cached items server-side. |
| export_data(cache_key, output_format, list_unpack?) | Dump the full dataset to json / jsonl / csv. Returns a download URL. |