ToolSnap MCP MCP server

ToolSnap MCP provides a suite of 47 server-side tools for AI agents, including web extraction, SEO analysis, document processing, and media generation. It operates on a reference-based model to save context tokens, offering 36 free tools and paid options via credit cards or crypto.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by ToolSnap

MCP endpoint (Streamable HTTP)

https://mcp.toolsnap.app/mcp

Vendor documentation

What you can do with it

Fetch and extract clean text or structured data from URLs
Perform SEO audits including keyword volume and sitemap crawling
Generate images, video, or transcribe audio using integrated models
Execute multi-tool workflows like site replication or data diffing

Tools advertised by the last live check:

tool_catalog
use_tool
task_recipes
memory_snippet
pricing
fetch_extract
fetch_html
html_to_markdown
fetch_metadata
pdf_text_extract
csv_query
json_query
sitemap_parse
rss_parse
screenshot_url
keyword_research
remove_background

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http toolsnap-mcp https://mcp.toolsnap.app/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add toolsnap-mcp --url https://mcp.toolsnap.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable toolsnap-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "toolsnap-mcp": {
      "url": "https://mcp.toolsnap.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "toolsnap-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.toolsnap.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start toolsnap-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "toolsnap-mcp": {
      "type": "http",
      "url": "https://mcp.toolsnap.app/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http toolsnap-mcp https://mcp.toolsnap.app/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "toolsnap-mcp": {
      "url": "https://mcp.toolsnap.app/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "toolsnap-mcp": {
      "serverUrl": "https://mcp.toolsnap.app/mcp"
    }
  }
}

See all 957

Do you run ToolSnap MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing