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