From 7f8ca5eed490360d3c694ea24bdff8f370ff9fec Mon Sep 17 00:00:00 2001 From: aakash Date: Thu, 27 Aug 2026 04:47:06 +0000 Subject: [PATCH] docs(mcp): document add_to_thread and thread tools (common#8237) Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- consensus-mcp.mdx | 84 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 84 insertions(+) diff --git a/consensus-mcp.mdx b/consensus-mcp.mdx index ac4d997..fc1dfd8 100644 --- a/consensus-mcp.mdx +++ b/consensus-mcp.mdx @@ -302,6 +302,90 @@ Each search returns: - "Recent research on large language model hallucination from top tier journals" - "Use Consensus Deep Research to compare evidence for different treatments for insomnia" +## Research thread tools + +The Consensus MCP server exposes research-thread tools for multi-turn, agentic research. Use `create_thread` to start a new thread and `add_to_thread` to continue an existing thread with a new follow-up. + +### `create_thread` + +Creates a new research thread and dispatches the Consensus research agent. Use this for detailed, synthesis, comparison, or multi-step research questions. For a simple list of papers, prefer the `search` tool. + +#### Parameters + +| Parameter | Type | Required | Description | +| --- | --- | --- | --- | +| input_message | string | Yes | Your complete research brief. Include the full question, scope, constraints, and any ordered sub-tasks. | +| mode | string | No | Research depth. `pro` (default, fast) or `deep` (multi-step literature review, requires a signed-in paid caller). | +| filters | object | No | Optional structured filters. Supports the same keys as the Search Tool. | +| attachments | object | No | Optional attachments. `{"paper_attachments": [{"paper_id": "...", "es_hash_paper_id": "..."}], "collection_ids": [123]}`. | + +### `add_to_thread` + +Adds a new interaction to an existing research thread. Use this only for a genuinely new follow-up after seeing the previous interaction's results. Do not use it to decompose a single request across multiple calls — put the whole request in the `create_thread` brief instead. + +#### Parameters + +| Parameter | Type | Required | Description | +| --- | --- | --- | --- | +| thread_id | string | Yes | The `thread_id` returned by `create_thread`. | +| input_message | string | Yes | A new follow-up question. The agent uses thread context and can reference papers from earlier turns. | +| mode | string | No | Research depth. `pro` (default) or `deep` (requires a signed-in paid caller). | +| title | string | No | The thread title from the `create_thread` response. Used only for the deep-link label; if omitted, the URL uses an `untitled` slug. | +| filters | object | No | Optional structured filters. Supports the same keys as `create_thread`. | +| attachments | object | No | Optional attachments. Same shape as `create_thread`. | + +### Dispatch response + +Both tools return an immediate dispatch confirmation while the agent runs asynchronously. + + + The thread identifier. + + + + The new interaction identifier. + + + + The thread title used in the deep-link label. + + + + `running` while the agent is working. + + + + `pro` or `deep`. + + + + Direct link to view the thread in Consensus. + + + + Human-readable confirmation with the Consensus link. + + + + Whether the result should be displayed first. + + + + Minimum seconds to wait before polling for completion (30). + + + + Maximum recommended wait time: 180 seconds for `pro`, 600 seconds for `deep`. + + + + Polling instructions for the model. + + + + `deep` mode requires a signed-in paid Consensus account. Free accounts that request `deep` will receive a paid-account error. + + ## Troubleshooting