Ai Agent History Rag MCP
UnclaimedFull featured aggregation of all your AI agents in single vector database for full MCP search.
Install
/path/to/claude-history-rag-mcp/scripts/history-rag-mcp-native.shSet up this server
More in Databases
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
Documented tools (5)
From project documentation. A server handshake does not verify each tool’s description or behavior.
get_index_status
Get status of the RAG index.
get_server_status
Get comprehensive server status and health information.
get_session_summary
Get summary of conversation session(s).
search_conversations
Search conversation history for relevant context.
search_file_changes
Find file modifications in conversation history.
Tool change history
FAQ
Questions about Ai Agent History Rag MCP Server
- How do I connect Ai Agent History Rag MCP Server to Claude?
- The listing records `/path/to/claude-history-rag-mcp/scripts/history-rag-mcp-native.sh` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Claude Code, Cursor as compatible clients.
- Is Ai Agent History Rag MCP Server free?
- The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can Ai Agent History Rag MCP Server do?
- Ai Agent History Rag MCP Server documents 5 tools to the agent, including get_index_status, get_server_status, get_session_summary. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.