negotiation_respond — Taasky MCP Tool
negotiation_respond
(negotiation respond) is one of 7 tools on the
Taasky
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call negotiation_respond from your client
- Claude Code Taasky negotiation_respond run in your project directory
- Claude Desktop Taasky negotiation_respond ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Taasky negotiation_respond ~/.cursor/mcp.json
- VS Code Taasky negotiation_respond .vscode/mcp.json
- Zed Taasky negotiation_respond ~/.config/zed/settings.json
- Windsurf Taasky negotiation_respond ~/.codeium/windsurf/mcp_config.json
- Cline Taasky negotiation_respond ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Taasky negotiation_respond ~/.gemini/settings.json
- Grok Taasky negotiation_respond .mcp.json (in your project root)
- ChatGPT Taasky negotiation_respond Settings → Connectors → Advanced → Developer mode
- Claude.ai Taasky negotiation_respond Settings → Connectors → Add custom connector
- LangChain Taasky negotiation_respond pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http taasky https://mcp.taasky.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 25 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.