analyze_account — glim.sh MCP Prompt

analyze_account is one of 3 prompts on the glim.sh MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke analyze_account from your client

• Claude Code glim.sh Prompt/analyze_account run in your project directory
• Claude Desktop glim.sh Prompt/analyze_account ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor glim.sh Prompt/analyze_account ~/.cursor/mcp.json
• VS Code glim.sh Prompt/analyze_account .vscode/mcp.json
• Zed glim.sh Prompt/analyze_account ~/.config/zed/settings.json
• Windsurf glim.sh Prompt/analyze_account ~/.codeium/windsurf/mcp_config.json
• Cline glim.sh Prompt/analyze_account ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI glim.sh Prompt/analyze_account ~/.gemini/settings.json
• Grok glim.sh Prompt/analyze_account .mcp.json (in your project root)
• ChatGPT glim.sh Prompt/analyze_account Settings → Connectors → Advanced → Developer mode
• Claude.ai glim.sh Prompt/analyze_account Settings → Connectors → Add custom connector
• LangChain glim.sh Prompt/analyze_account pip install langchain-mcp-adapters

Other prompts on this server

• research_topic
• monitor_sentiment

glim.sh also offers 6 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.