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