MCP Connector
Put HTMLToolz inside Claude, Cursor, and agent workflows.
The paid MCP connector exposes production HTMLToolz API tools through the Model Context Protocol. Use it to format JSON, clean HTML, decode tokens, generate hashes, convert text, and run developer utilities directly inside your assistant.
Hosted connector
Add https://htmltoolz.com/api/mcp to clients that support remote MCP over HTTP.
Tool runner
The hosted connector uses the same documented paid API tool runner and batch-safe transforms.
Paid entitlement
All paid plans include mcp_access. Free API keys still work for extension license checks, but not MCP tool calls.
Use a tool pack
Copy a tested MCP prompt from a pack, then run the same work from Claude, Cursor, Windsurf, or any MCP-capable assistant.
Browse MCP-ready packs Workflow recipesWhat the connector unlocks
/api/v1/me, can be revoked, and inherit the same paid-plan gate as the REST API.Connect hosted MCP
Best when your client supports custom remote connectors or Streamable HTTP MCP. Use the API key from your account page as a Bearer token.
| Field | Value |
|---|---|
| Server URL | https://htmltoolz.com/api/mcp |
| Authorization | Bearer htk_live_YOUR_KEY |
| Transport | Streamable HTTP, stateless JSON responses |
| Plan | Pro, Team, or Agency |
Claude Code
claude mcp add --transport http htmltoolz https://htmltoolz.com/api/mcp \ --header "Authorization: Bearer htk_live_YOUR_KEY"
Claude.ai / Claude Desktop custom connector
URL: https://htmltoolz.com/api/mcp Authorization header: Bearer htk_live_YOUR_KEY
Local stdio package status
The Node stdio server lives in the repo for packaging and private distribution, but the public npm package is not published yet. Use the hosted endpoint above for customer-facing installs today.
Repo-based development config
{
"mcpServers": {
"htmltoolz": {
"command": "node",
"args": ["C:/path/to/htmltoolz/mcp/src/cli.js"],
"env": {
"HTMLTOOLZ_API_KEY": "htk_live_YOUR_KEY"
}
}
}
}
Claude Code repo development
claude mcp add htmltoolz --env HTMLTOOLZ_API_KEY=htk_live_YOUR_KEY -- node C:/path/to/htmltoolz/mcp/src/cli.js
Smoke test the remote server
These calls prove the connector is reachable, authenticated, and returning tool results.
Initialize
curl -s -X POST https://htmltoolz.com/api/mcp \
-H "Authorization: Bearer htk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'
List tools
curl -s -X POST https://htmltoolz.com/api/mcp \
-H "Authorization: Bearer htk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'
Call a tool
curl -s -X POST https://htmltoolz.com/api/mcp \
-H "Authorization: Bearer htk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"json_formatter","arguments":{"input":"{\"hello\":\"world\"}","options":{"minify":false}}}}'
MCP vs REST API
| Use MCP when | Use the REST API when |
|---|---|
| You want tools inside Claude, Cursor, Windsurf, or an MCP-capable agent. | You want direct calls from CI, scripts, server jobs, client dashboards, or internal products. |
You want assistant-native tool discovery through tools/list. | You want a stable HTTP endpoint like /api/v1/tools/run or /api/v1/batch. |
| You want the broad shared catalog. | You want the production REST subset with documented inputs, rate limits, and batch limits. |