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