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