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