Developer · Local MCP server
RCLL
Self-hosted shared memory for a team of AI agents. Rooms, L0-L3 depth, no LLM on the read path.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.rcll/fleet-memory- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-28
- Updated
- 2026-08-28
- Publisher
- ai.rcll
- Namespace
- Namespace verified by the MCP Registry via the domain rcll.ai · how
- Website
- rcll.ai
- Repository
- github.com/Holetron-lab/fleet-memory
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | fleet-memory-mcp | 0.1.0 | stdio |
How to connect RCLL
RCLL runs locally from a Node.js package published to the npm registry: fleet-memory-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y fleet-memory-mcp@0.1.0. It reads these environment variables: FLEET_URL and FLEET_BANK; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"fleet-memory": {
"command": "npx",
"args": [
"-y",
"fleet-memory-mcp@0.1.0"
],
"env": {
"FLEET_URL": "<value>",
"FLEET_BANK": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, rcll.ai, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More developer servers
| Server | Runs |
|---|---|
| Raw SQL MCPExecute raw SQL queries against SQL Server, SQLite, PostgreSQL, MySQL, and MariaDB. | Local · stdio |
| RaygunInvestigate errors, track deployments, analyze performance, and manage application monitoring. | Remote · HTTPLive check: sign-in required |
| Razi Dev UtilitiesDeveloper utilities over MCP: Base64 encode and decode, decode JWTs, format JSON, do percentages. | Remote · HTTPLive check: ✓ handshake |
| RazielMCP server teaching AI agents to implement TideCloak: auth, E2EE, IGA, security analysis. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| RE-call MCP Memory ServerAgent memory on your own Postgres that flags superseded facts and abstains instead of guessing. | Local · stdio |
| REAReverse engineer anything from your terminal or agent with one CLI and MCP server. | Local · stdio |
| Reachpad MCPCoding agents build full-stack apps in persistent workspaces and share them by link. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Read Only Local Postgres MCP ServerMCP server for read-only PostgreSQL database queries in Claude Desktop. | Local · stdio |