5 #history MCP Servers & Clients
Every MCP server and client below is tagged #history — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to history tools.
All
Fyndling
neongrau
Built for medieval market fans, reenactors, and living-history enthusiasts — and the AI assistants that help them plan. Fyndling MCP gives AI clients direct access to two niche European datasets:
Claude Historian
Vvkmnn
claude-historian - an MCP server that gives Claude access to your your previous messages and conversations.
flatten-mcp
shayaShav
An MCP server that flattens Claude Code sessions — keeping every prompt and event verbatim while reclaiming context tokens, so you resume the exact same raw conversation at a lower token count instead of compacting it into a lossy summary. It moves bulky tool output (large file r
Chron
SirinivasK
AI tools show when you sent a message. Chron logs when the AI responded too — and keeps a permanent, queryable record of every exchange across every tool you use. Works with Claude Desktop, Claude Code, Cursor, Windsurf, and any MCP-compatible AI tool. Every exchange is stored wi
Terminal History Mcp
HasanJahidul
terminal-history-mcp gives AI agents (Claude Code, Cursor, Cline, Zed, any MCP client) full-text search over your shell history.
Frequently asked questions
What is a #history MCP server?
- An MCP server tagged #history implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access history-related tools, data, or APIs.
How many #history MCP servers and clients are there?
- mcp.so currently lists 5 MCP servers and clients tagged #history.
How do I install a #history MCP server?
- Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.