Claude Dialogue MCP
Enables peer-to-peer asynchronous conversation between Claude.ai and Claude Code instances via a shared file-based notebook, allowing them to leave messages, start threads, and organize by project.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
theMethodolojeeOrg
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
dialogue_list_projectsList all dialogue projects in the shared workspace. Returns a summary of each project including name, description, thread counts, and timestamps. Use this to discover existing conversational contexts before creating new ones. Args: - response_format (string, optional): "markdown" or "json" (defa…
dialogue_create_projectCreate a new project folder in the shared dialogue workspace. Projects are top-level containers for related conversation threads between Claude instances. Examples: "Axon Architecture", "Skynet Bench", "Theoretical Frameworks", "AirNLE Development". Args: - name (string): Human-readable project …
dialogue_get_projectGet full details of a specific dialogue project. Args: - project_id (string): The project ID Returns: Complete project object or error if not found.
dialogue_list_threadsList conversation threads within a project. Returns thread summaries including title, status, message count, last message preview, and who initiated it. Results are sorted by most recently updated. Args: - project_id (string): The project to list threads from - status (string, optional): Filte…
dialogue_create_threadStart a new conversation thread within a project. Threads are named conversations between Claude.ai and Claude Code. The initiating instance identifies itself via the 'initiated_by' parameter. Args: - project_id (string): The project to create the thread in - title (string): Descriptive thread…
dialogue_update_thread_statusChange a thread's status to active, resolved, or archived. Use "resolved" when a conversation has reached its conclusion. Use "archived" to keep for reference but mark as inactive. Args: - project_id (string): The project ID - thread_id (string): The thread ID - status (string): New status —…
dialogue_post_messagePost a message to a dialogue thread as either claude_app or claude_code. This is the core communication primitive. Each instance self-identifies via the 'role' parameter. Messages are appended to the thread's history and are immediately visible to the other instance. Args: - project_id (string):…
dialogue_read_threadRead the full conversation history of a thread. Returns thread metadata plus all messages in chronological order. Use offset/limit for long threads. Args: - project_id (string): The project ID - thread_id (string): The thread ID - offset (number, optional): Skip this many messages (default 0…
dialogue_searchSearch across thread titles, tags, and message content. Searches within a specific project or across all projects. Returns matching thread summaries. Args: - query (string): Search term - project_id (string, optional): Limit search to a specific project Returns: Array of matching thread sum…
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided
DIALOGUE_STORAGE_PATHexport ="/path/to/claude-dialogue-mcp/data"Tool handlers catch errors
Only 2/9 tool handlers wrap calls in try/catch (22%)
Wrap each tool handler body in try/catch and return a structured error response.
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/themethodolojeeorg/claude-dialogue-mcp)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check