order_think_tank_session_30 — Taste MCP Tool
order_think_tank_session_30
(order think tank session 30) is one of 20 tools on the
Taste
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call order_think_tank_session_30 from your client
- Claude Code Taste order_think_tank_session_30 run in your project directory
- Claude Desktop Taste order_think_tank_session_30 ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Taste order_think_tank_session_30 ~/.cursor/mcp.json
- VS Code Taste order_think_tank_session_30 .vscode/mcp.json
- Zed Taste order_think_tank_session_30 ~/.config/zed/settings.json
- Windsurf Taste order_think_tank_session_30 ~/.codeium/windsurf/mcp_config.json
- Cline Taste order_think_tank_session_30 ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Taste order_think_tank_session_30 ~/.gemini/settings.json
- Grok Taste order_think_tank_session_30 .mcp.json (in your project root)
- ChatGPT Taste order_think_tank_session_30 Settings → Connectors → Advanced → Developer mode
- Claude.ai Taste order_think_tank_session_30 Settings → Connectors → Add custom connector
- LangChain Taste order_think_tank_session_30 pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http taste-mcp https://api.humantaste.app/mcp/Other tools on this server
- list_offerings
- list_expert_profiles
- get_result
- prepare_consult_domain_expert
- request_think_tank_revision
- request_illustration_revision
- verify_external_source
- review_content
- verify_reasoning_chain
- prepublish_review
- predict_audience_reaction
- arbitrate_dispute
- request_human_approval
- verify_certificate
- order_think_tank_session_60
- consult_domain_expert
- ask_a_human
- review_plan
- review_code
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.