Anysite MCP Server
A hosted, paid server that returns structured LinkedIn data — profiles, people search, companies, posts, jobs, the Ad Library — plus a dozen other sources, with server-side filtering and export. No LinkedIn login goes anywhere near it, and it cannot write to LinkedIn at all. An Anysite API key or OAuth token. No LinkedIn login, cookie or grant is involved anywhere in the MCP path.
- Last read
What it is built for, and the jobs it cannot do
The second card is the one a repository README never contains. Both are written from the project's own documentation and source, read on 20 September 2026.
Pulling structured LinkedIn data at volume into Claude, Cursor or ChatGPT, with server-side filtering, aggregation and CSV or XLSX export, and without putting a LinkedIn login anywhere near the agent.
Any workflow where the agent must act on LinkedIn: posting, commenting, reacting, connection requests, messaging and InMail are all absent by design. Not for Sales Navigator search or Recruiter, both unavailable through MCP. Not for anyone wanting a free, self-hosted or credential-free option: it is a paid hosted service with no local mode.
- Publisher
- Anysite, Inc. — previously published as Horizon Data Wave — the vendor of the product it drives.
- Licence
- MIT — open client, closed service
- Version
- 3.0.0
- Runs
- Hosted by the vendor
- Transport
- stdio and Streamable HTTP
- Repository
- github.com/anysiteio/anysite-mcp-server
- Homepage
- anysite.io
- Last read
MIT, but only the stdio bridge is open. The repository holds four TypeScript files that proxy the hosted server; no data-collection logic is in it.
An Anysite API key or OAuth token. No LinkedIn login, cookie or grant is involved anywhere in the MCP path.
A third-party data vendor's key. No LinkedIn login, cookie or grant is involved, and the vendor's own infrastructure does the fetching.
No account of yours can be restricted, because no account of yours is used. You are instead paying someone else to do what LinkedIn’s terms forbid, so the exposure is contractual and legal rather than account-level.
No LinkedIn account is behind the server, or it acts only through LinkedIn’s own approved API and only to read. Nothing here can get an account restricted.
An Anysite API key or OAuth token created in the vendor dashboard, supplied as an environment variable to the stdio bridge, as a query parameter on the endpoint URL, or as a bearer header. An active paid subscription is required: without one, authorization fails with "Active subscription required. Please subscribe first." A request with no credential returns 401. MCP-plan keys work only through the MCP server; the same key sent to the REST API is rejected.
Account risk is derived from the authentication class and from whether the server writes to LinkedIn — not judged per project. The 5 classes and the rule that maps them are on the LinkedIn MCP server directory; the ceilings LinkedIn enforces on any account, automated or not, are on LinkedIn limits. What this particular server exposes, and what it does with your credentials, is below.
Its write tools land off LinkedIn, not on it
These are the tool names the server registers, as a client sees them. An assistant can call any tool the server exposes once it is connected, so the list below is the whole surface, not a feature summary.
- discover
- execute
- get_page
- query_cache
- merge_data
- export_data
- search_requests
- crm_list_connections
- crm_connect
- crm_connect_status
- crm_get_schema
- crm_query_records
- crm_upsert_contacts
- crm_upsert_companies
- crm_undo
All 15 tools it registers are named above. These are meta-tools. The LinkedIn endpoints are reached through discover and execute against a dynamic registry, so the tool names a client sees are not the names of the LinkedIn operations.
What it can read
11 read actions, written as what they return rather than as the tool signature.
- LinkedIn person profile, and profile sub-resources: experience, education, skills, certificates, honors, languages, patents, articles, endorsers.
- LinkedIn people search, including a SQL-style search surface.
- LinkedIn company profile, company posts and company employee statistics.
- LinkedIn post lookup, post comments, post reactions and reposts.
- A member's posts, comments and reactions.
- LinkedIn job lookup and job search; group lookup.
- LinkedIn Ad Library: ads, advertisers, an advertiser's ads, ad search.
- Email lookup and find-email-by-URL enrichment.
- Company, location, industry and education reference search.
- Non-LinkedIn sources through the same discover and execute pair: Instagram, X, Reddit, YouTube, SEC EDGAR, Y Combinator, Crunchbase, DuckDuckGo, a universal web parser and AI parsers for several marketplaces.
- Server-side paging, filtering, sorting, aggregation, merging and export to JSON, JSONL, CSV or XLSX, over results already fetched. A seven-day server-side cache; export URLs live 24 hours.
What it can write, and where the write lands
4 write actions, none of which touches LinkedIn. They change a vendor workspace, a connected system or a file on your own machine.
| Action | Where it lands | What it does |
|---|---|---|
crm_connect | Off LinkedIn | Starts an OAuth connection to HubSpot or Pipedrive. |
crm_upsert_contacts | Off LinkedIn | Writes contacts into the connected CRM, matched by email, record id or LinkedIn URL. |
crm_upsert_companies | Off LinkedIn | Writes companies into the connected CRM, matched by domain or record id. |
crm_undo | Off LinkedIn | Restores the values a write run changed. |
Read the middle column before the third. A write that lands off LinkedIn — a vendor workspace, a CRM, a local file — is undone by deleting a row. A write that lands on LinkedIn has already been seen by another member.
Installing it, in the project's own commands
Every command and every configuration block below is the project's own, copied unchanged on 20 September 2026. Where a project publishes no config block, this page says so rather than composing one — a snippet written here would be a snippet the maintainer never tested.
Hosted, Claude Code
claude mcp add --transport http anysite "https://mcp.anysite.io/mcp?api_key=YOUR_KEY"
claude mcp liststdio bridge, only for clients that cannot speak HTTP
npm install -g @anysiteio/mcpThe configuration block
Client config keys are not interchangeable, and a block pasted under the key a different client expects fails silently rather than erroring. That is why the blocks below are the project's own, in the clients it names, rather than one block normalised here.
stdio bridge
{
"mcpServers": {
"anysite": {
"command": "npx",
"args": ["-y", "@anysiteio/mcp"],
"env": {
"ANYSITE_ACCESS_TOKEN": "your_token_here"
}
}
}
}Cursor
{
"mcpServers": {
"anysite": {
"url": "https://mcp.anysite.io/mcp?api_key=YOUR_KEY",
"transport": "http"
}
}
}Nothing beyond a paid Anysite account on the recommended path — the server is hosted and reached over streamable HTTP, so a client that speaks HTTP needs nothing installed. No Docker, no headless browser, no database, no LinkedIn account. Only if the client is stdio-only: Node 20 or newer and the bridge package. A paid subscription is mandatory.
Claude Desktop (OAuth custom connector; Tool access must be set to "Tools already loaded", or the generic discover and execute names are not reliably matched); Claude Code; Cursor; Cline; Windsurf; ChatGPT; Grok; n8n; Make; Clay. Where the file goes in each Claude surface. The same block in Cursor. What a ChatGPT connector can and cannot reach.
streamable-http for the hosted server; stdio through the bridge package for clients that cannot speak HTTP.
Hosted only. The server runs at mcp.anysite.io; the npm package is a stdio-to-HTTP bridge, not a self-hostable server. The v3 migration notes put it plainly: "the package no longer reimplements the server locally — it proxies the hosted MCP server." There is no Dockerfile and no local mode.
The vendor's own figures, quoted rather than computed
No free tier: authorization fails without an active subscription. From the pricing page on 20 September 2026 — MCP plans at $30, $99 and $199 a month; usage-based API plans that also include MCP access from $49 a month for 15,000 credits up to $1,199 for 1.2 million, plus a custom tier. The README describes the $30 tier as "MCP Unlimited ($30/month, 6 req/min fair-use, no credit counting)" and offers a promo covering the first month. Metering on MCP plans runs in five-hour and weekly windows, returning 429 on exhaustion, with LinkedIn endpoints carrying their own windows.
The underlying REST API documents a Sales Navigator people search, but the docs list it among the endpoints explicitly excluded from the MCP server. It was reachable in version 2 and the v3 notes say it is now "excluded by server policy".
No LinkedIn Recruiter endpoints exist in the API reference. The only recruiting-adjacent sources are unrelated applicant tracking systems.
None of the figures above are LinkedIn's. They are third-party prices in the currency and the tiering each project publishes, read on 20 September 2026 and quoted rather than converted.
The code has moved recently
45 days between the last code change and the day these figures were read. Code changed within 90 days of the day this directory was checked.
Created March 2025 as horizondatawave/hdw-mcp-server, then renamed and rewritten. The npm package has shipped eight releases between October 2025 and August 2026. The repository has not been pushed since August, but the product behind it is moving: the vendor docs list tools the README does not yet mention, and the marketing site's sitemap was regenerated on 17 September 2026. Treat the repository as a thin, rarely-changing client for a live service.
Active means code changed within 90 days of the observation date; stale means up to 365 days. It is measured from the last change to code, not to the README, and never from the maintainer's own adjective. Anything past a year is dropped from this directory rather than published as dormant.
- Stars
- 64
- Last commit
- — The repository holds exactly one commit: history was squashed at the v3 rewrite, so the earlier Horizon Data Wave commits are gone although closed pull requests and issues back to March 2025 remain visible.
- Open issues
- 1 — The single open item is an unsolicited directory-listing request, not a defect. 0 open pull requests.
- Status
- Active
- Observed
Every figure in this section was read from GitHub on , and star and issue counts move daily. The issue count is the Issues tab, not the API field of the same name — that one counts pull requests as issues and overstates every repository in this directory.
What to check before you point it at a real account
Both cards below are read from the repository and its own security documentation. A project saying what it does with a session is evidence of intent, not proof of behaviour.
No LinkedIn credential is ever supplied to this server and it performs no action on a LinkedIn account, so it carries no direct ban risk to your own profile — the account-safety question that applies to cookie-session tools does not apply. The risk is of a different kind: the data is obtained by a third-party scraping vendor rather than through LinkedIn's official API, which is contrary to LinkedIn's prohibition on scraping, and the legal exposure sits with the vendor and with how the buyer uses the data. Note separately that the wider Anysite platform can act through a LinkedIn account connected to it — connection requests, chat messages, posts and comments — through its REST API and an automation node. That path does carry account risk, and it is exactly the path excluded from MCP. The Acceptable Use Policy prohibits unsolicited mass messaging and bulk outreach, fake accounts, engagement manipulation and activity that infringes third-party rights or contractual terms, and reserves the right to suspend accounts without notice.
The query-parameter connection form puts a live credential in a URL, which the README itself flags: "The URL carries your API key — treat it as a secret." Exports return a download URL that is accessible without a token, protected only by an unguessable filename and valid 24 hours; the README warns not to share it if the data is sensitive. Fetched data sits in a server-side cache for seven days, shared across your sessions. An OAuth connection lasts 30 days. Cancelling a long call stops the client waiting but not the server processing, and the work is still billed. All queried data passes through Anysite's infrastructure.
2 things that will waste an hour
Small, checkable and specific to this project — a stale package name, a broken link, a manifest that advertises something the code removed.
- The README's local-development section gives a clone URL that 404s; the repository name has a -server suffix the URL is missing.
- The README advertises five general tools where the vendor docs describe seven.
The servers that do a comparable job, and how they differ
Same rows, same sources, same observation date. The first column is this server.
| Anysite MCP Serverv3.0.0 | Bright Data MCP (LinkedIn tools)v2.11.3 | Insaightv0.1.0 | |
|---|---|---|---|
| Authenticates with | Vendor API key | Vendor API key | Vendor API key |
| Account risk | Low | Low | Low |
| Writes to LinkedIn | None | None | None |
| Tools registered | 15 | 69 | 18 |
| Sales Navigator tools | No | No | No |
| Recruiter tools | No | No | No |
| Runs | Hosted by the vendor | Either | Self-hosted |
| Last code change | 6 August 2026 — active | 15 September 2026 — active | 31 August 2026 — active |
| Licence | MIT, open client, closed service | MIT, open source | MIT, open source |
Bright Data MCP (LinkedIn tools)
Vendor API keyA general web-access server with five LinkedIn extractors: hand it a profile, company, job, post or people-search URL and it returns structured JSON. It holds no LinkedIn credential, so there is no account to restrict.
stdio and Streamable HTTP69 toolsRead 20 September 2026Insaight
Vendor API keyResearch and record-keeping for manual outreach: it briefs you on a person or a company, mines a post's comment thread, and keeps a local ledger of what you sent and what replied. It has no send path at all.
stdio18 toolsRead 20 September 2026
Every page this profile was read from
8 pages — the repository, its documentation and, where one exists, the vendor's own pricing page. Nothing on this profile is summarised from another directory or from a blog post about the project.
- github.com/anysiteio/anysite-mcp-server
- raw.githubusercontent.com/anysiteio/anysite-mcp-server/main/README.md
- api.github.com/repos/anysiteio/anysite-mcp-server
- api.github.com/repos/anysiteio/anysite-mcp-server/commits
- registry.npmjs.org/@anysiteio/mcp
- anysite.io/pricing
- app.anysite.io/docs
- mcp.anysite.io/mcp
All of them read on . A repository moves faster than a price does: if a tool list or a command here no longer matches the project, the project changed and this page has not been re-read yet.
Check what it cannot reach before you build on it
No account of yours can be restricted, because no account of yours is used. You are instead paying someone else to do what LinkedIn’s terms forbid, so the exposure is contractual and legal rather than account-level.