check_permitted_development — Site Pack MCP Tool Read-only
check_permitted_development
(check permitted development) is one of 8 tools on the
Site Pack
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_permitted_development from your client
- Claude Code Site Pack check_permitted_development run in your project directory
- Claude Desktop Site Pack check_permitted_development ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Site Pack check_permitted_development ~/.cursor/mcp.json
- VS Code Site Pack check_permitted_development .vscode/mcp.json
- Zed Site Pack check_permitted_development ~/.config/zed/settings.json
- Windsurf Site Pack check_permitted_development ~/.codeium/windsurf/mcp_config.json
- Cline Site Pack check_permitted_development ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Site Pack check_permitted_development ~/.gemini/settings.json
- Grok Site Pack check_permitted_development .mcp.json (in your project root)
- ChatGPT Site Pack check_permitted_development Settings → Connectors → Advanced → Developer mode
- Claude.ai Site Pack check_permitted_development Settings → Connectors → Add custom connector
- LangChain Site Pack check_permitted_development pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http site-pack https://site-pack.nerolabs.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.