Memory for your
coding agent.

Keep what your agent tried, what happened, and which checks passed. Mentis gives developers a record of earlier work that their agents can use again.

Each task has a history.
Each attempt has evidence.

Your agent sends records through MCP. Mentis stores them in Neo4j, linked by repository and task. Failed attempts stay beside successful ones, so the next agent can see what happened.

Attempt records
Mentis MCP
Stored in
Neo4j
Repository
TaskFix the login loop
Check failed

Change the redirect

The browser returns to sign-in.

Check passed

Keep the session cookie

The browser stays signed in.

What it keeps

Actions, observations, affected file names, and code context. Add an inference, evidence references, Git state, or a check result when available. A check that did not run stays unverified.

What it does not collect

Mentis does not scan your files or copy your conversation. It stores only what your agent sends. Keep secrets out of records. Search queries and attempt text go to OpenRouter for search processing.

See the memory
your agent can use.

Login returns to the sign-in page

src/Login.tsx

Record an attempt.
Keep the result.

Codex keeps the session cookie over local HTTP and runs a browser test. It saves the action, observation, and result together.

The observation states what happened. An optional inference states what the agent thinks it means.

Action
Retain the session cookie over local HTTP
Observation
The browser stays signed in after login
Inference
No inference recorded
Check
browser testCheck passed

Connect your agent.

Choose your agent and copy its setup. Sign in with Google when you connect. No local server or database is required.

Remote MCP setup

Add this URL to a client that supports HTTP MCP servers and OAuth sign-in.

MCP server URL
https://mcp.men-tis.xyz/mcp