render_page — Signal Desk paid tools MCP Tool
render_page
(render page) is one of 5 tools on the
Signal Desk paid tools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call render_page from your client
- Claude Code Signal Desk paid tools render_page run in your project directory
- Claude Desktop Signal Desk paid tools render_page ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Signal Desk paid tools render_page ~/.cursor/mcp.json
- VS Code Signal Desk paid tools render_page .vscode/mcp.json
- Zed Signal Desk paid tools render_page ~/.config/zed/settings.json
- Windsurf Signal Desk paid tools render_page ~/.codeium/windsurf/mcp_config.json
- Cline Signal Desk paid tools render_page ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Signal Desk paid tools render_page ~/.gemini/settings.json
- Grok Signal Desk paid tools render_page .mcp.json (in your project root)
- ChatGPT Signal Desk paid tools render_page Settings → Connectors → Advanced → Developer mode
- Claude.ai Signal Desk paid tools render_page Settings → Connectors → Add custom connector
- LangChain Signal Desk paid tools render_page pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http signal-desk https://x402-mcp.huntercarver24.workers.dev/mcpOther tools on this server
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.