Convo History MCP
Fetches conversation data directly from a PostgreSQL database, rendering it as formatted terminal output.
Click on "Install 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 MCPShow 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.
Convo History MCP
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.
Why Convo History MCP?
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: PostgreSQL MCP Server
Quick Start
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.
Environment Variables
Variable | Description | Required |
| PostgreSQL connection string | Yes |
Database Schema
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 messagesclick- User interactions (rendered as[clicked: option_1])output_list- Option menus with emojis and descriptionsrecommendation- Summaries with cost estimates
Features
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 |
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
This project is licensed under the MIT License - see the LICENSE file for details.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceProvides read-only access to local Beeper message history on macOS, enabling users to search conversations, read messages, and list recent chats through natural language queries. Supports both SQLite and IndexedDB storage formats with privacy-focused local-only operation.1
- Alicense-qualityDmaintenanceEnables interaction with PostgreSQL databases through both HTTP and stdio transports. Supports executing read-only SQL queries, listing tables, and retrieving schema information with stateful session management.34MIT
- Alicense-qualityBmaintenanceIndexes and searches agent conversation logs from Antigravity and Cursor workspaces, enabling semantic search, token analysis, and benchmarking over local SQLite storage.19MIT
- AlicenseAqualityCmaintenanceImports private ChatGPT conversations into MCP clients like Codex and Claude Code. Provides tools to fetch remote conversation content and serve cached context via local stdio.41MIT
Related MCP Connectors
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…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/rreinold/convo-history-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server