get_competitive_context — Persimmon MCP Tool Read-only
get_competitive_context
(get competitive context) is one of 3 tools on the
Persimmon
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_competitive_context from your client
- Claude Code Persimmon get_competitive_context run in your project directory
- Claude Desktop Persimmon get_competitive_context ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Persimmon get_competitive_context ~/.cursor/mcp.json
- VS Code Persimmon get_competitive_context .vscode/mcp.json
- Zed Persimmon get_competitive_context ~/.config/zed/settings.json
- Windsurf Persimmon get_competitive_context ~/.codeium/windsurf/mcp_config.json
- Cline Persimmon get_competitive_context ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Persimmon get_competitive_context ~/.gemini/settings.json
- Grok Persimmon get_competitive_context .mcp.json (in your project root)
- ChatGPT Persimmon get_competitive_context Settings → Connectors → Advanced → Developer mode
- Claude.ai Persimmon get_competitive_context Settings → Connectors → Add custom connector
- LangChain Persimmon get_competitive_context pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http persimmon https://mcp.persimmonhq.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.