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