Claude Dialogue MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIALOGUE_STORAGE_PATH | No | Set the storage path (defaults to ~/.claude-dialogue) | ~/.claude-dialogue |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dialogue_list_projectsA | List 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:
Returns: Array of project summaries with id, name, description, thread_count, active_thread_count, timestamps. |
| dialogue_create_projectA | Create 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:
Returns: The created project object with generated ID and timestamps. |
| dialogue_get_projectA | Get full details of a specific dialogue project. Args:
Returns: Complete project object or error if not found. |
| dialogue_list_threadsA | List 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:
Returns: Paginated list of thread summaries. |
| dialogue_create_threadA | Start 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:
Returns: The created thread object with generated ID and timestamps. |
| dialogue_update_thread_statusA | Change 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:
Returns: Updated thread object. |
| dialogue_post_messageA | Post 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:
Returns: The created message object with generated ID and timestamp. |
| dialogue_read_threadA | Read the full conversation history of a thread. Returns thread metadata plus all messages in chronological order. Use offset/limit for long threads. Args:
Returns: Thread metadata and paginated message history. |
| dialogue_searchA | Search across thread titles, tags, and message content. Searches within a specific project or across all projects. Returns matching thread summaries. Args:
Returns: Array of matching thread summaries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: project vs. thread vs. message, and create/list/get/update/post/read/search are clearly separated. No two tools overlap in purpose.
All tools follow a consistent dialogue_ verb_noun (or verb_noun_noun) snake_case pattern, e.g., dialogue_create_thread, dialogue_list_projects. The naming is predictable and uniform.
9 tools is well-scoped for a dialogue management server, covering project, thread, message, and search operations without unnecessary redundancy or bloat.
Core dialogue workflows are fully covered: create project, create/read/update threads, post/read messages, search. Minor gaps exist such as no update/delete for projects and no delete for threads, but archive covers thread lifecycle.