Claude Desktop Wicked MCP identity_submit_response
How to: Claude Desktop Wicked MCP identity_submit_response
Add Wicked MCP to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"wicked-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.wickedapi.com/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
Ask for something identity_submit_response does. Claude Desktop lists the server's tools on connect and calls identity_submit_response 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 Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs
Set these first
Wicked MCP will not start until these are set, so identity_submit_response 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 3 October 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.