validate_token_permissions — JSONPad documentation MCP Tool
validate_token_permissions
(validate token permissions) is one of 14 tools on the
JSONPad documentation
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call validate_token_permissions from your client
- Claude Code JSONPad documentation validate_token_permissions run in your project directory
- Claude Desktop JSONPad documentation validate_token_permissions ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor JSONPad documentation validate_token_permissions ~/.cursor/mcp.json
- VS Code JSONPad documentation validate_token_permissions .vscode/mcp.json
- Zed JSONPad documentation validate_token_permissions ~/.config/zed/settings.json
- Windsurf JSONPad documentation validate_token_permissions ~/.codeium/windsurf/mcp_config.json
- Cline JSONPad documentation validate_token_permissions ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI JSONPad documentation validate_token_permissions ~/.gemini/settings.json
- Grok JSONPad documentation validate_token_permissions .mcp.json (in your project root)
- ChatGPT JSONPad documentation validate_token_permissions Settings → Connectors → Advanced → Developer mode
- Claude.ai JSONPad documentation validate_token_permissions Settings → Connectors → Add custom connector
- LangChain JSONPad documentation validate_token_permissions pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http docs https://mcp.jsonpad.io/docsOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 7 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.