Skip to main content
Glama
theMethodolojeeOrg

Claude Dialogue MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DIALOGUE_STORAGE_PATHNoSet 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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:

  • response_format (string, optional): "markdown" or "json" (default: "json")

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:

  • name (string): Human-readable project name

  • description (string, optional): What this project is about

  • metadata (string, optional): JSON string of arbitrary structured data (framework references, etc.)

Returns: The created project object with generated ID and timestamps.

dialogue_get_projectA

Get 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_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:

  • project_id (string): The project to list threads from

  • status (string, optional): Filter by status (active/resolved/archived)

  • offset (number, optional): Pagination offset (default 0)

  • limit (number, optional): Max results (default 20)

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:

  • project_id (string): The project to create the thread in

  • title (string): Descriptive thread title

  • initiated_by (string): "claude_app" or "claude_code" — who is starting this thread

  • tags (string, optional): Comma-separated tags for categorization and search

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:

  • project_id (string): The project ID

  • thread_id (string): The thread ID

  • status (string): New status — "active", "resolved", or "archived"

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:

  • project_id (string): The project containing the thread

  • thread_id (string): The thread to post to

  • role (string): "claude_app" or "claude_code" — who is posting

  • content (string): The message content — can be prose, code, structured notes, whatever serves the conversation

  • metadata (string, optional): JSON string of structured data — framework references, decision records, code pointers, etc.

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:

  • project_id (string): The project ID

  • thread_id (string): The thread ID

  • offset (number, optional): Skip this many messages (default 0)

  • limit (number, optional): Max messages to return (default 50)

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:

  • query (string): Search term

  • project_id (string, optional): Limit search to a specific project

Returns: Array of matching thread summaries.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/theMethodolojeeOrg/claude-dialogue-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server