anysite-mcp-server

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

claude mcp add --transport http anysite "https://mcp.anysite.io/mcp?api_key=YOUR_KEY"
claude mcp list   # should show: anysite connected

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:

{
  "mcpServers": {
    "anysite": {
      "url": "https://mcp.anysite.io/mcp?api_key=YOUR_KEY",
      "transport": "http"
    }
  }
}

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:

What MCP tools do you have from anysite?

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

Use anysite to find 20 CTOs at Series B fintech startups in New York,
then show me the ones with AI or ML in their headline.

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

npm install -g @anysiteio/mcp

Or run on demand with `npx -y @anysiteio/mcp`.

Configure your client

{
  "mcpServers": {
    "anysite": {
      "command": "npx",
      "args": ["-y", "@anysiteio/mcp"],
      "env": {
        "ANYSITE_ACCESS_TOKEN": "your_token_here"
      }
    }
  }
}

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

Sources surfaced through `discover`: LinkedIn, Instagram, Twitter/X, Reddit, YouTube, SEC EDGAR, Y Combinator, Crunchbase, DuckDuckGo, the universal web parser, plus AI parsers for GitHub, Amazon, Google Maps, G2, BuiltWith, Apify, GLEIF, Newegg and more. New endpoints appear automatically as soon as they ship on the platform.

Data fetched by `execute` is cached server-side for 7 days: one `execute()` call, then unlimited `get_page` / `query_cache` / `export_data` calls without re-paying API credits. Export files live for 24 hours (regenerated on demand while the cache entry is alive).

Usage pattern

discover("linkedin", "search")
  → endpoints: ["users", "companies", "posts", ...] with params

execute("linkedin", "search", "users", { keywords: "CTO AI" })
  → { items: [...first 10], total: 50, cache_key: "abc..." , next_offset: 10 }

get_page("abc...", offset=10)            # next page, free
query_cache("abc...", { conditions: [{ field: "location", op: "contains", value: "San Francisco" }] })
export_data("abc...", "csv")             # full dataset as a CSV download URL

The agent figures out the parameter names on its own from `discover`.

Migrating from 2.x

v3 is a breaking change: the package no longer reimplements the server locally — it proxies the hosted MCP server. What changes for you:

• `export_data` returns a download URL (`https://mcp.anysite.io/exports/…`) instead of a local file path. The `file_path` field is gone; agents that read the exported file from disk must download it instead. The URL is accessible without a token (the file name is unguessable) and lives for 24 hours — do not share the link if the data is sensitive.
• `export_data` parameter is `output_format`. The old `format` name is transparently rewritten by the bridge for backward compatibility, but new prompts should use `output_format`.
• `get_page` caps `limit` at 50 (server-side page size limit).
• Cache is server-side now (7-day TTL, survives restarts, shared across your sessions) instead of in-process.
• CRM tools appear (8 `crm_*` tools) when the CRM integration is enabled on your account.
• Env vars `ANYSITE_API_URL` and `ANYSITE_OPENAPI_URL` are removed — the bridge talks to the MCP server, not the raw API. Use `ANYSITE_MCP_URL` to point at a different MCP server.
• `bin` aliases `anysite` and `mcp` are removed — the command is `anysite-mcp`.
• Two LinkedIn endpoints that were reachable in 2.x (`sn_search/users`, `company/employees`) are excluded by server policy.
• Tool results no longer carry a `mimeType` on content items — the server defines the response shape.
• Cancelling a long `tools/call` stops the client-side wait, but the server keeps processing the request (stateless transport cannot deliver the cancellation) — the work is still billed.

Skills — ready-made workflows

The MCP server gives raw access. Anysite Skills package that access into named workflows you summon by topic, so the assistant runs a proven pattern instead of improvising. Built for Claude Code (also works in Cursor / Windsurf via the same plugin format).

Full catalog (17 skills, including VC analyst, influencer discovery, audience analysis, content analytics, trend analysis): github.com/anysiteio/agent-skills.

Install

In Claude Code:

/plugin marketplace add https://github.com/anysiteio/agent-skills
/plugin install anysite-lead-generation@anysite-skills

You can install one skill or the whole marketplace. The MCP server connection above is the only prerequisite.

Local development

git clone https://github.com/anysiteio/anysite-mcp.git
cd anysite-mcp
npm install
npm run build:tsc
ANYSITE_ACCESS_TOKEN=... node build/server.js

Inspect the tools interactively:

npm run inspector

Configuration

Variables can also live in `./.env` or `~/.anysite-mcp.env` (real environment variables and `./.env` take precedence over `~/.anysite-mcp.env`).

If the remote server is unreachable at startup, the bridge still starts in a degraded mode (empty tool list, descriptive errors on calls), keeps reconnecting in the background, and announces the tool list via `tools/list_changed` once the server is reachable again.

Project layout

src/
├── server.ts   stdio entry (CLI bin): env handling, connect with retries, degraded mode
├── proxy.ts    the bridge: remote client, generic request forwarding, tools/list cache,
│               format→output_format shim, error mapping, background list refresh
├── index.ts    Smithery TypeScript runtime adapter
└── config.ts   env-derived constants

License

MIT