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