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