About this integration
Repository engineering context served from a bitemporal Neo4j graph through read, analytic, and governed write MCP tools.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Package
- memex-mcp
- Last compatibility test
- Not independently tested
Connect your agent
memex-mcpThis is the distinct Python memex-mcp artifact; the existing stifler-memex-mcp npm listing is not treated as its alias. Documented from publisher files only; not executed. Write and review workflows are excluded.
Capabilities: retrieve bounded project context, retrieve symbol context, search engineering context, list recent decisions and open problems, predict change impact
Connected profiles
Additional details
memex-mcp
Source ↗ · Checked 2026-09-190.9.0
Source ↗ · Checked 2026-09-19The qualified scope covers the documented read and analytic tools plus automatic read-only prefetch. Write tools, human validation, and intent-confirmation flows are excluded.
Source ↗ · Checked 2026-09-19Operation requires Neo4j connection credentials and a Gemini API key. This combined database/API prerequisite does not fit a single native authentication class.
Source ↗ · Checked 2026-09-19The Python artifact declares the memex console entry point; publisher client configurations launch its serve subcommand as an MCP process.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19