BaseMouse
About
One shared, versioned memory for your AI agents across Claude Code, Cursor, Kiro and Grok, with a source on every answer and full history.
Details
- Author
- Unknown
- Categories
- AI, Knowledge Base
Jump to
capability matrix verified in production
Point BaseMouse at a folder of your docs. It reads them, keeps every version, and labels them so they're easy to find. Re-import whenever you like, with no duplicates, and a clear report if any file doesn't go through.
YOUR AGENT ASKS, AND GETS SOURCED ANSWERS
Your agent makes one request and gets back the most relevant passages, each with its source, a fingerprint that proves it hasn't been tampered with, and how recently it was updated. Ready to drop straight into a prompt.
Every change is recorded, and nothing is ever silently overwritten. Even deletions stay on the record. So you can always answer two questions: where did this answer come from, and what changed since?
Register each tool once — Claude Code, Cursor, Codex, Grok, and more. Every one reads the same grounded context, and whatever an agent writes back in one tool is there for an agent in another, even a different vendor. Your docs and your agents' memory move with you; only the live chat stays inside each tool.
BaseMouse is a remote MCP server atPOST https://basemouse.com/mcp. Add it once and every agent reads and writes the same memory.
Omit the header to browse the public demo corpus. Add your Bearer key for your own workspace.
- search— find relevant context
- get_context_pack— an agent-ready bundle
- upsert_document— persist decisions by stable id
claude mcp add --transport http basemouse https://basemouse.com/mcp \ --header "Authorization: Bearer bm_..."
{ "mcpServers": { "basemouse": { "url": "https://basemouse.com/mcp", "headers": { "Authorization": "Bearer bm_..." } } } }
The demo docs need no key. Your documents need one header.
For your engineers: it's a single HTTP call, no SDK to install. The endpoints below show exactly what comes back.
- GET /api/context-pack— cited, checksummed pack
- GET /api/search— ranked matches with scores
- POST /api/documents— your docs in (Bearer bm_…)
- GET /api/documents/:id/history— the full record
curl -s "https://basemouse.com/api/context-pack?q=agent%20context&limit=2"
{ "schema": "basemouse.context_pack.v1", "entryCount": 2, "citations": [ { "label": "[agent-context-engine] …" } ], "entries": [ { "title": "Agent Context Engine", "relevance": { "score": 6, "matchedTerms": ["agent","context"] }, "provenance": { "checksum": "e765f4dce81039b4", "version": 3 } } ] }
Pick a plan → pay → key issued instantly, shown once. Billed through Stripe. BaseMouse never sees your card.
BaseMouse isopen source at its heart. The engine that imports your docs and serves sourced answers is free and MIT-licensed. Run it on your own servers, with nothing phoning home. The paid hosted version just handles the running, billing, and support for you, so you don't have to. See the docs for exactly which features ship today versus what's on the roadmap.
It's a place to store the documents your AI agents read from. You import your docs, your agent asks a question over one API call, and it gets back the most relevant passages with a source on each one. Every change to every document is kept on the record, so you can always check where an answer came from.
How is this different from a vector database or building RAG myself?
A vector database gives you one ingredient. BaseMouse is the finished dish: import, search, citations, tamper-proof fingerprints, and full change history behind a single endpoint. No pipeline to build, no SDK to install, nothing to keep in sync.
Folders of markdown today. Labels in your files are kept and made searchable, and re-importing is always safe: no duplicates, and a clear report if a file doesn't go through. Docs can also stay in sync on their own: a GitHub Action pushes a repo's agent docs on every push, and a small cross-platform CLI syncs a whole projects folder — or watches it and pushes the moment you save. Bringing docs from another source? That's exactly what thedesign partner programis for.
No. BaseMouse stores your documents and serves passages back to your own agents. That's the whole job. Our operational telemetry never includes document contents, and if you self-host the core, your docs never leave your servers at all.
Yes. The core engine is MIT-licensed and self-hostable, with no license key and nothing phoning home. The paid hosted version adds the running, billing, and support. Grab iton GitHub.
One HTTP call, from any language or agent framework. The demo needs no key at all, and your own docs need one header. Seethe API sectionfor the exact request and response. Prefer a native connection? BaseMouse speaks the Model Context Protocol atPOST /mcp, so agents like Claude Code, Cursor, Codex CLI, Gemini CLI, and Grok CLI connect directly — the samesearchandget_context_packtools, plusupsert_documentso an agent canwrite its own decisions back(idempotently — unchanged content writes nothing), same auth and quota.
Both. Reading is the common case — grounded, cited context packs — but agents can also persist notes and decisions by stable id via the API (?mode=upsert) or theupsert_documentMCP tool. Every write is a versioned, append-only revision, so it doubles as durable agent memory across sessions without ever losing history.
Yes. Point each tool at BaseMouse once, and every one of them — Claude Code, Cursor, Codex, Grok, and more — reads thesamegrounded context. Anything an agent writes back is immediately readable by an agent in adifferenttool, even a different vendor: your knowledge and your agents' memory travel with you. (The live chat inside each tool stays local to it — BaseMouse is the shared knowledge and memory layer, not a transcript-sync service.)
Persistent memory for AI assistants and coding agents across ChatGPT, Claude, Cursor, and other MCP-compatible tools.
Operational memory for AI agents that persists across sessions and tools.
MCP (Model Context Protocol) server that exposes 70 tools spanning cognitive memory, working memory, sessions, agents, the L0–L3 knowledge hierarchy, orchestration tasks, and training pipelines. The server speaks stdio and is consumed by Claude Desktop, Claude Code, OpenCodex, and any MCP-aware client.
MEMANTO is a memory agent. It remembers, recalls, and answers — so your agents can achieve long-term goals and avoid confusion.
A local-first, LLM-agnostic memory layer for AI assistants
Hosted MCP memory across Claude Code, Cursor, ChatGPT and any MCP client. Community-hosted instance of the MIT-licensed MemPalace engine. EU-hosted, GDPR-compliant. Free tier with 200 memories.
Shared memory layer for AI coding agents with dream pipeline distillation, session grounding, and multi-instance coherence.
Your portable context layer — load it into any AI.
AI Reasoning Cache & Consensus Layer with 50+ reasoning objects across 14 domains. Cache hit/miss with token savings, failure risk check before execution, cross-model verification, and citation tracking. 11 MCP tools via Streamable HTTP.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.


