Fetches conversation data directly from a PostgreSQL database, rendering it as formatted terminal output.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Convo History MCP Show me the conversation with ID abc-123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Render conversation history as beautiful, human-readable terminal output.
An MCP server that fetches conversations directly from PostgreSQL and displays them as elegantly formatted dialogues. Built for the Model Context Protocol.
Ever stared at walls of JSON trying to debug a conversation? Yeah, us too.
Convo History MCP fetches conversation data straight from your database and renders it as clean, readable terminal output with proper alignment, text wrapping, and visual separation between user and assistant messages.
================================================================================
CONVERSATION: 26b2889f-1c8b-446e-ad85-917b378cfd80
================================================================================
USER:
------------------------------------------------------------
What's the weather like in San Francisco?
--------------------------------------------------------------------------------
ASSISTANT:
--------------------------------------------------------------------------------
Based on current conditions, San Francisco is experiencing mild
temperatures around 65°F with partly cloudy skies. Perfect weather
for a walk along the Embarcadero!
================================================================================
END OF CONVERSATION
================================================================================Related MCP server: chronicle-mcp
claude mcp add --transport stdio convo-history --scope local \
-e 'DATABASE_URL=${DATABASE_URL}' \
-- docker run -i --rm -e DATABASE_URL ghcr.io/rreinold/convo-history-mcp:latestOr add to your ~/.claude.json:
{
"mcpServers": {
"convo-history": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "DATABASE_URL",
"ghcr.io/rreinold/convo-history-mcp:latest"
],
"env": {
"DATABASE_URL": "postgres://user:pass@host:5432/dbname"
}
}
}
}That's it. Claude Code will now have access to your conversation history.
Variable | Description | Required |
| PostgreSQL connection string | Yes |
The server expects the following tables:
CREATE TABLE conversations (
id UUID PRIMARY KEY,
chat_session_id VARCHAR UNIQUE,
created_at TIMESTAMP
);
CREATE TABLE conversation_messages (
id UUID PRIMARY KEY,
conversation_id UUID REFERENCES conversations(id),
user_input JSONB,
assistant_response JSONB
);Message Format:
{
"user_input": {"method": "chat", "message": "Hello!"},
"assistant_response": {"answer": "Hi there! How can I help?"}
}Supported Message Types:
chat - Standard text messages
click - User interactions (rendered as [clicked: option_1])
output_list - Option menus with emojis and descriptions
recommendation - Summaries with cost estimates
Feature | Description |
Direct DB Access | Fetches conversations via psql, no intermediate files |
Smart Text Wrapping | Preserves paragraphs, wraps to 60 chars |
Visual Alignment | User messages right-aligned, assistant left-aligned |
Rich Content | Supports options, recommendations, costs |
MCP Native | Built for Model Context Protocol |
Contributions are welcome! Please feel free to submit a Pull Request.
This project is licensed under the MIT License - see the LICENSE file for details.
This server cannot be deployed
Run AI customer support from your terminal: conversations, knowledge base, and chat widget.
Query PostgreSQL databases in plain English — LLM-generated, safety-validated SQL.
Explore your Messages SQLite database to browse tables and inspect schemas with ease. Run flexible…
Generate, fix, explain and run read-only SQL on PostgreSQL, MySQL and SQL Server
