disasm.dev MCP server

A Model Context Protocol server for disasm.dev. It lets an AI assistant (Claude, Cursor, and any MCP client) generate valid DataDome and Incapsula clearance tokens, without a headless browser.

It is built for development and prototyping: solve a challenge inline and have your assistant wire the result into your scraper. Production traffic should call the HTTP API directly.

Tools

Every tool uses one disasm.dev API key. Create one in the dashboard.

Related MCP server: sessemi-mcp

Install (local, stdio)

Add it to your MCP client. For Claude Desktop, edit claude_desktop_config.json:

{
  "mcpServers": {
    "disasm": {
      "command": "npx",
      "args": ["-y", "disasm-mcp"],
      "env": { "DISASM_API_KEY": "your_api_key" }
    }
  }
}

The same command / args / env shape works for Cursor and other clients.

Use (remote, HTTP)

The server also runs as a remote Streamable HTTP endpoint. Point your client at the URL and pass your key as a Bearer token:

{
  "mcpServers": {
    "disasm": {
      "url": "https://mcp.disasm.dev/mcp",
      "headers": { "Authorization": "Bearer your_api_key" }
    }
  }
}

The hosted endpoint is stateless: each request carries its own key and no key is stored server-side.

Run it yourself

npm install
npm run build

# stdio (what npx runs)
DISASM_API_KEY=your_api_key npm start

# remote HTTP on :8787 (override with PORT)
npm run start:http

Configuration

Notes

• Treat your API key like a password. Anyone with it can spend your balance.

License

MIT. See LICENSE.