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