English Français العربية

StremAI

Official registry Developer tools

StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http stremai 'https://stremai.com/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "stremai": {
            "type": "http",
            "url": "https://stremai.com/api/mcp"
        }
    }
}
NPM package aiagentsbay-mcp
Claude Code 
claude mcp add stremai -- npx -y aiagentsbay-mcp@1.2.5
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "stremai": {
            "command": "npx",
            "args": [
                "-y",
                "aiagentsbay-mcp@1.2.5"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. StremAI
  2. Use StremAI when
  3. The short version
  4. Connect Claude Code
  5. Connect another MCP client
  6. Local package fallback
  7. What StremAI remembers
  8. Useful entry points
  9. Install guides
  10. Comparison reads
  11. About this repo
  12. License

StremAI

One brain for all your coding agents.

StremAI is a shared memory layer for AI coding agents. Connected agents in tools like Claude Code, Cursor, Codex, and other MCP-compatible clients can store what they learn while working, and other connected agents can recall it later across sessions, machines, and tools.

Memory is user-controlled: entries are human-readable, attributed to the agent that stored them, and can be exported, archived, or erased from StremAI.

Use StremAI when

  • You keep re-explaining the same repo, conventions, or decisions to every new agent session
  • Context disappears between sessions, or when you switch machines
  • One agent learns something — a pitfall, a fix, an architectural decision — and your other agents have no idea
  • Handoff notes go stale and nothing tells an agent which version still applies
  • You use more than one coding tool and want them to share context instead of starting from zero

The short version

  • Hosted MCP first. Connect https://stremai.com/api/mcp with OAuth/browser sign-in where your MCP client supports it.
  • Works with the tools developers already use. Claude Code, Cursor, Codex, Windsurf, OpenClaw, Hermes, and other MCP clients can use the same memory layer.
  • API keys are the fallback. Use them for CI, scripts, or clients that cannot complete OAuth/browser sign-in.
  • Compatibility names remain. Some packages and tools still use the original agentbay or aiagentsbay-mcp names so existing installs keep working.

Connect Claude Code

claude mcp add --transport http stremai https://stremai.com/api/mcp --scope user

Then approve the sign-in in your browser. The --scope user flag makes the connection available outside the current project directory.

Connect another MCP client

Use the hosted endpoint:

{
  "mcpServers": {
    "stremai": {
      "type": "http",
      "url": "https://stremai.com/api/mcp"
    }
  }
}

If your client cannot complete OAuth/browser sign-in, create an API key in StremAI and use a Bearer header:

{
  "mcpServers": {
    "stremai": {
      "type": "http",
      "url": "https://stremai.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ab_live_your_key_here"
      }
    }
  }
}

Local package fallback

For stdio-only clients or local experiments:

npx -y aiagentsbay-mcp@latest

The package name is legacy compatibility; new docs and server aliases use stremai.

Python:

pip install stremai
from stremai import StremAI

brain = StremAI()
brain.store("JWT auth uses 24h refresh tokens", title="Auth pattern", type="PATTERN")
brain.recall("authentication")

What StremAI remembers

StremAI is for the learned layer that accumulates while agents work:

  • decisions and architectural context
  • setup gotchas and repo-specific commands
  • pitfalls that cost time once and should not cost time again
  • handoffs between Claude Code, Cursor, Codex, and teammates
  • project facts that should be available to the next connected agent

Keep your instruction files. CLAUDE.md, AGENTS.md, and project READMEs hold instructions you write. StremAI holds the memory agents learn while working.

Useful entry points

Install guides

Comparison reads

About this repo

This is StremAI's public install, comparison, scorecard, and MCP recipe surface. The repository name remains agentbay for compatibility with older links and package metadata.

The hosted application and some SDK implementation details are developed separately. File public docs issues here, and we route product or package issues internally when needed.

License

MIT for everything in this repository.

Frequently asked questions

What is StremAI?

StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio.

How do I install StremAI?

It runs as a remote server. In Claude Code: claude mcp add --transport http stremai 'https://stremai.com/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does StremAI need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is StremAI open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains StremAI?

It is published by thomasjumper. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.