get_conversations — Parsley - Buyer Intent Signals MCP Tool Read-only
get_conversations
(get conversations) is one of 8 tools on the
Parsley - Buyer Intent Signals
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_conversations from your client
- Claude Code Parsley - Buyer Intent Signals get_conversations run in your project directory
- Claude Desktop Parsley - Buyer Intent Signals get_conversations ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Parsley - Buyer Intent Signals get_conversations ~/.cursor/mcp.json
- VS Code Parsley - Buyer Intent Signals get_conversations .vscode/mcp.json
- Zed Parsley - Buyer Intent Signals get_conversations ~/.config/zed/settings.json
- Windsurf Parsley - Buyer Intent Signals get_conversations ~/.codeium/windsurf/mcp_config.json
- Cline Parsley - Buyer Intent Signals get_conversations ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Parsley - Buyer Intent Signals get_conversations ~/.gemini/settings.json
- Grok Parsley - Buyer Intent Signals get_conversations .mcp.json (in your project root)
- ChatGPT Parsley - Buyer Intent Signals get_conversations Settings → Connectors → Advanced → Developer mode
- Claude.ai Parsley - Buyer Intent Signals get_conversations Settings → Connectors → Add custom connector
- LangChain Parsley - Buyer Intent Signals get_conversations pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http parsley-mcp https://www.parsley.id/api/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.