Claude.ai Wicked MCP chain_block
How to: Claude.ai Wicked MCP chain_block
Add Wicked MCP to Claude.ai
-
01
Open Settings → Connectors → Add custom connector and merge this in. Keep any servers already there.
https://mcp.wickedapi.com/mcp-
02
Save the file and restart Claude.ai.
-
03
Ask for something chain_block does. Claude.ai lists the server's tools on connect and calls chain_block itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Wicked MCP's identifier in your config matches the one above exactly.
Claude on the web takes a remote URL and completes OAuth in the browser. For a packaged server use Claude Desktop or Claude Code instead. Claude.ai docs
Set these first
Wicked MCP will not start until these are set, so chain_block never becomes available.
-
WICKEDAPI_API_KEY -
WICKEDAPI_PAYER_PRIVATE_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.