wrap_up_day — giteasy MCP Prompt

wrap_up_day is one of 4 prompts on the giteasy MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke wrap_up_day from your client

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

Other prompts on this server

• save_and_share
• start_new_work
• whats_going_on

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.