@anakin-io/mcp

@anakin-io/mcp

Model Context Protocol server for Anakin.

Gives AI agents in Claude Desktop, Cursor, Windsurf, VS Code, and any other MCP-compatible client native access to web scraping, search, crawling, mapping, agentic research, and Wire actions — without writing any glue code.

Status: alpha (v0.1.x). Tool surface and arguments may change between minor versions until v1.0.

Quick install (recommended)

One command configures every detected agent client:

npx -y @anakin-io/mcp@latest init --all

You'll be prompted for your API key (or set ANAKIN_API_KEY first to skip the prompt). Get one free at anakin.io/dashboard — 500 credits, no card required.

After it finishes, restart your agent client(s). The anakin MCP server will appear in the tool list, exposing the tools below.

Manual install

If you prefer to edit config files yourself, see Manual setup per client.

What's exposed

Tool	Purpose
scrape	Fetch one URL → markdown (or AI-extracted JSON with generateJson: true).
search	AI web search with citations. Synchronous.
map	Discover all URLs on a domain.
crawl	Bulk-fetch markdown across a site.
agentic_search	Multi-source deep research (1–5 min).
wire_discover	Find a Wire action for a task by natural-language intent.
wire_catalog	Browse supported sites and a site's actions + param schemas.
wire_action	Run a pre-built Wire action (read or write) and get its result.
wire_identities	List saved accounts/credentials for auth-required actions.
wire_login	Sign in to a credentials-mode site → credential_id.
wire_build	Request a brand-new action for a site not yet in the catalog.

Wire runs pre-built automation actions across hundreds of sites. Actions are read (extract listings, category products, prices, reviews, profiles, dashboard metrics) or write (log in, checkout, submit a form) — many read actions need no auth. The loop is: wire_discover (or wire_catalog) to find an action_id, then wire_action to run it; add a credential_id only when the action's auth mode is required.

Each tool is a thin wrapper around the Anakin REST API — there is no scraping logic in this package, just MCP-protocol glue. The HTTP client is self-contained (src/client.ts); no runtime dependency on the @anakin-io/sdk Node SDK.

Updating

The configs here pin @anakin-io/mcp@latest, so every time your client launches the server, npx resolves and runs the newest published version — just restart your client to pick up a release.

If your config uses an unpinned @anakin-io/mcp (no @latest), npx can keep serving an older cached build. Refresh it once:

rm -rf ~/.npm/_npx        # clear npx's install cache, then restart your client

Confirm which version you're running:

npx -y @anakin-io/mcp@latest --version

Manual setup per client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "anakin": {
      "command": "npx",
      "args": ["-y", "@anakin-io/mcp@latest"],
      "env": {
        "ANAKIN_API_KEY": "ak-..."
      }
    }
  }
}

Restart Claude Desktop.

Claude Code (Anthropic CLI)

Edit ~/.claude/settings.json:

{
  "mcpServers": {
    "anakin": {
      "command": "npx",
      "args": ["-y", "@anakin-io/mcp@latest"],
      "env": {
        "ANAKIN_API_KEY": "ak-..."
      }
    }
  }
}

Or use Claude Code's built-in command:

claude mcp add anakin npx -y @anakin-io/mcp@latest -e ANAKIN_API_KEY=ak-...

Cursor

Edit ~/.cursor/mcp.json (user-scoped) or ./.cursor/mcp.json (project-scoped):

{
  "mcpServers": {
    "anakin": {
      "command": "npx",
      "args": ["-y", "@anakin-io/mcp@latest"],
      "env": {
        "ANAKIN_API_KEY": "ak-..."
      }
    }
  }
}

Restart Cursor.

Cline (VS Code extension — "Claude Dev")

Edit Cline's settings file inside VS Code's globalStorage:

Platform	Path
macOS	~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Linux	~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Windows	%APPDATA%/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

{
  "mcpServers": {
    "anakin": {
      "command": "npx",
      "args": ["-y", "@anakin-io/mcp@latest"],
      "env": {
        "ANAKIN_API_KEY": "ak-..."
      }
    }
  }
}

Reload the Cline VS Code extension (or restart VS Code).

Continue (IDE extension)

Edit ~/.continue/config.json:

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "name": "anakin",
        "command": "npx",
        "args": ["-y", "@anakin-io/mcp@latest"],
        "env": {
          "ANAKIN_API_KEY": "ak-..."
        }
      }
    ]
  }
}

If you have other entries under experimental.modelContextProtocolServers, append the anakin object to the existing array — don't overwrite. Reload the Continue extension.

Zed

Edit ~/.config/zed/settings.json (macOS / Linux) or %APPDATA%/Zed/settings.json (Windows):

{
  "context_servers": {
    "anakin": {
      "command": "npx",
      "args": ["-y", "@anakin-io/mcp@latest"],
      "env": {
        "ANAKIN_API_KEY": "ak-..."
      }
    }
  }
}

Reload Zed.

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "anakin": {
      "command": "npx",
      "args": ["-y", "@anakin-io/mcp@latest"],
      "env": {
        "ANAKIN_API_KEY": "ak-..."
      }
    }
  }
}

Restart Windsurf.

VS Code (with the MCP extension)

Edit .vscode/mcp.json in your workspace:

{
  "servers": {
    "anakin": {
      "command": "npx",
      "args": ["-y", "@anakin-io/mcp@latest"],
      "env": {
        "ANAKIN_API_KEY": "ak-..."
      }
    }
  }
}

Reload VS Code.

Verify it's working

In Claude Desktop / Cursor / etc., ask the agent something like:

Scrape https://example.com using anakin and return the markdown.

The agent should call the scrape tool, return the page contents, and cite the call in its trace.

CLI reference

anakin-mcp                       Run the MCP server (default — clients spawn this).
anakin-mcp init                  Interactive client config.
anakin-mcp init --all            Configure every detected client, no prompts.
anakin-mcp init --client=cursor  Only configure one client.
anakin-mcp --version             Print version.
anakin-mcp --help                Print usage.

How agents discover Anakin

Two complementary paths:

• MCP (this package) — for clients that support it. Tools are typed and called natively. This is the high-quality path.
• SKILL.md — for any agent that can fetch a URL. The markdown describes the API end-to-end so an agent can use it via plain HTTP calls.

Most users on Claude Desktop / Cursor / Windsurf / VS Code will want option 1.

Development

git clone https://github.com/Anakin-Inc/anakin-mcp.git
cd anakin-mcp
npm install
npm run build
ANAKIN_API_KEY=ak-... node dist/cli.js  # smoke-test the server

For local end-to-end testing with an actual MCP client, point the client at the absolute path of dist/cli.js:

{
  "mcpServers": {
    "anakin-dev": {
      "command": "node",
      "args": ["/absolute/path/to/anakin-mcp/dist/cli.js"],
      "env": { "ANAKIN_API_KEY": "ak-..." }
    }
  }
}

Related

• @anakin-io/sdk — Node.js / TypeScript SDK
• anakin — Python SDK
• anakin-cli — Python CLI for human terminal use
• SKILL.md — agent-onboarding doc for non-MCP agents

License

Apache 2.0