discoverLABSCO SUMMARY
One fetch, then page and query it for free.
The cache is the mechanism that makes the five-tool design pay off: execute costs credits once, and then get_page, query_cache and export_data all run server-side against the 7-day cache without re-charging — so narrowing and exporting a large result is cheap. The discover-before-execute pattern is what lets one small tool set cover dozens of sources: the agent reads the endpoint's parameters from discover rather than needing a bespoke tool per site.
What it is
Anysite's official server, exposing dozens of data sources through five universal tools plus an optional set of CRM write-back tools. It runs as a hosted Streamable HTTP server with OAuth, with an npm stdio bridge for clients that only speak stdio.
What you get
- discover lists the endpoints in a category for a source, with their parameters and LLM hints — always called before execute, so the agent learns the parameter names on its own rather than guessing
- execute fetches data from a source's endpoint and returns the first 10 items plus a cache_key
- get_page paginates the cached items without re-fetching (limit up to 50), so one execute call feeds unlimited paging without re-paying credits
- query_cache filters, sorts and aggregates the cached items server-side by conditions, sort_by, aggregate and group_by, narrowing a large result set without pulling it all back
- export_data dumps the full dataset to json, jsonl or csv and returns a download URL
- Sources surfaced through discover include LinkedIn, Instagram, Twitter/X, Reddit, YouTube, SEC EDGAR, Y Combinator, Crunchbase and DuckDuckGo, plus a universal web parser and AI parsers for GitHub, Amazon, Google Maps, G2 and more — new endpoints appear automatically as they ship
- An optional set of eight crm_* tools for HubSpot-and-friends read/write — connections, schema, upsert of contacts and companies, query and undo — visible only when the CRM integration is enabled on your account
- Fetched data is cached server-side for 7 days, so paging, querying and exporting off one execute call cost no additional API credits
Requirements
An Anysite account from anysite.io on a paid MCP plan. Connect directly to the hosted server at https://mcp.anysite.io/mcp over Streamable HTTP with OAuth — if your client speaks HTTP you do not need the npm package. For stdio-only clients, the @anysiteio/mcp bridge needs an ANYSITE_ACCESS_TOKEN, which can live in ~/.anysite-mcp.env. In Claude Desktop, set tool access to 'Tools already loaded', or the generic names discover and execute will not be reliably matched.
Setup effort
One command plus a key — npm install -g @anysiteio/mcp, then supply credentials
USE CASES
01
Pulling a list off a source you don't know the API for
Discover the source's search endpoints and their parameters, execute the one that fits, and let the agent figure out the parameter names from what discover returned.
02
Working a large result without re-fetching
After one execute, page through the cached items and filter, sort or aggregate them server-side to find the subset you want — all against the cache, no extra credits.
03
Handing the data off
Export the full cached dataset to CSV or JSONL and get a download URL, so the result can go into a spreadsheet or another tool.
5 tools
Listed in project docs. Your client may show a different list.
executeget_pagequery_cacheexport_dataBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation. Eight more crm_* tools, the only ones that write to HubSpot and similar CRMs, appear only when CRM is enabled for your account. The thousands of endpoints the vendor cites are reached through execute, not separate tools.
Requires
- npx on PATH
- ANYSITE_ACCESS_TOKEN in your environment
INSTALLATION
Connect your client
Server setup
npm
TERMINAL
npm install -g @anysiteio/mcpHosted endpoint
ENDPOINT URL
https://mcp.anysite.io/mcp?api_key=<YOUR_API_KEY>Add this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http anysite "https://mcp.anysite.io/mcp?api_key=<YOUR_API_KEY>"Cursor
CURSOR · JSON
{
"mcpServers": {
"anysite": {
"url": "https://mcp.anysite.io/mcp?api_key=<YOUR_API_KEY>"
}
}
}Any MCP client — stdio
ANY MCP CLIENT — STDIO · JSON
{
"mcpServers": {
"anysite": {
"command": "npx",
"args": [
"-y",
"@anysiteio/mcp"
],
"env": {
"ANYSITE_ACCESS_TOKEN": "<YOUR_ANYSITE_ACCESS_TOKEN>"
}
}
}
}
