Skip to main content
Glama
Asar007

visualize-chat-mcp

by Asar007
README.md
# Visualize Chat MCP

MCP server that visualizes Claude conversations as mindmaps.

Works with **Claude Desktop**, **Claude Web**, and **Claude Code CLI**.

## Install

```bash
npm install -g visualize-chat-mcp
```

## Setup

### Claude Desktop / Claude Web

Add to config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):

```json
{
  "mcpServers": {
    "visualize-chat": {
      "command": "npx",
      "args": ["-y", "visualize-chat-mcp"]
    }
  }
}
```

### Claude Code CLI

Add to `~/.claude.json`:

```json
{
  "mcpServers": {
    "visualize-chat": {
      "command": "npx",
      "args": ["-y", "visualize-chat-mcp"]
    }
  }
}
```

## Usage

Type `/visualize` in any Claude conversation.

Claude will:
1. Read the entire conversation
2. Generate a mindmap JSON
3. Save it to `~/.visualize-chat/visualizations/`

## Tools

| Tool | Description |
|------|-------------|
| `export_json` | Save mindmap to local file |
| `push_to_navigate` | Upload to Navigate Chat (requires API config) |

## Navigate Chat API (Optional)

To push visualizations to Navigate Chat, add env vars:

```json
{
  "mcpServers": {
    "visualize-chat": {
      "command": "npx",
      "args": ["-y", "visualize-chat-mcp"],
      "env": {
        "NAVIGATE_CHAT_API_URL": "http://localhost:8000",
        "NAVIGATE_CHAT_EMAIL": "your-email",
        "NAVIGATE_CHAT_PASSWORD": "your-password"
      }
    }
  }
}
```

## Output Format

```json
{
  "metadata": { "topic": "...", "contentType": "mindmap", "nodeCount": 15 },
  "nodes": [
    { "id": "root", "data": { "label": "Main Topic", "type": "root", "summary": "...", "hoverSummary": "..." } },
    { "id": "cat1", "data": { "label": "Category", "type": "category", "summary": "...", "hoverSummary": "..." } },
    { "id": "leaf1", "data": { "label": "Detail", "type": "leaf", "summary": "...", "hoverSummary": "..." } }
  ],
  "edges": [
    { "id": "e1", "source": "root", "target": "cat1", "type": "connects" }
  ],
  "hierarchy": {
    "root": ["cat1", "cat2"],
    "cat1": ["leaf1", "leaf2"]
  }
}
```

## License

MIT

TDQS

B3.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one saves visualization JSON to a local file, the other pushes it to an API. There is no overlap in their primary functions, so an agent can easily choose the correct one based on the desired destination.

Naming Consistency4/5

Both tool names use snake_case and start with imperative verbs (export, push). The pattern differs slightly—'export_json' is verb + object, while 'push_to_navigate' includes a preposition—but they remain readable and follow a similar style.

Tool Count3/5

With only two tools, the set feels thin for a general visualization server. However, for the narrow scope of exporting and pushing visualizations, the count is borderline acceptable rather than clearly insufficient.

Completeness4/5

The tools cover the two primary output paths (local save and remote API push), which covers the core workflow. Minor gaps exist, such as no listing or deletion of saved visualizations, but these are not dead ends for the main use case.

Maintenance

ActivityInactive
ResponsivenessNo issues