check_my_progress — anatome MCP Prompt
check_my_progress
is one of 8 prompts on the
anatome
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke check_my_progress from your client
- Claude Code anatome Prompt/check_my_progress run in your project directory
- Claude Desktop anatome Prompt/check_my_progress ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor anatome Prompt/check_my_progress ~/.cursor/mcp.json
- VS Code anatome Prompt/check_my_progress .vscode/mcp.json
- Zed anatome Prompt/check_my_progress ~/.config/zed/settings.json
- Windsurf anatome Prompt/check_my_progress ~/.codeium/windsurf/mcp_config.json
- Cline anatome Prompt/check_my_progress ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI anatome Prompt/check_my_progress ~/.gemini/settings.json
- Grok anatome Prompt/check_my_progress .mcp.json (in your project root)
- ChatGPT anatome Prompt/check_my_progress Settings → Connectors → Advanced → Developer mode
- Claude.ai anatome Prompt/check_my_progress Settings → Connectors → Add custom connector
- LangChain anatome Prompt/check_my_progress pip install langchain-mcp-adapters
Other prompts on this server
anatome also offers 8 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.