read_conversation — TraydStar MCP Tool Read-only
read_conversation
(read conversation) is one of 29 tools on the
TraydStar
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call read_conversation from your client
- Claude Code TraydStar read_conversation run in your project directory
- Claude Desktop TraydStar read_conversation ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TraydStar read_conversation ~/.cursor/mcp.json
- VS Code TraydStar read_conversation .vscode/mcp.json
- Zed TraydStar read_conversation ~/.config/zed/settings.json
- Windsurf TraydStar read_conversation ~/.codeium/windsurf/mcp_config.json
- Cline TraydStar read_conversation ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TraydStar read_conversation ~/.gemini/settings.json
- Grok TraydStar read_conversation .mcp.json (in your project root)
- ChatGPT TraydStar read_conversation Settings → Connectors → Advanced → Developer mode
- Claude.ai TraydStar read_conversation Settings → Connectors → Add custom connector
- LangChain TraydStar read_conversation pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http marketplace https://traydstar.com/mcp
Other tools on this server
- search_listings
- get_listing
- get_profile
- create_listing
- set_listing_status
- save_listing
- list_saved_listings
- list_my_listings
- update_listing
- remove_listing
- list_proposals
- create_proposal
- counter_proposal
- accept_proposal
- decline_proposal
- withdraw_proposal
- send_message
- list_conversations
- mark_conversation_read
- list_handshakes
- get_handshake
- confirm_handshake
- complete_handshake
- withdraw_handshake
- nudge_handshake
- get_wallet_link_message
- link_wallet
- verify_handshake_payment
This list was read from the server itself, by connecting to it and calling tools/list on 16 October 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.