OneDroid Engram

What OneDroid Engram MCP server does

OneDroid Engram MCP server is intended for agent memory stored in a Postgres database that you control. Its stated scope combines four properties: memory is versioned, context is portable, access is permissioned, and activity has an audit trail. These characteristics make it relevant when an agent's retained context needs more structure and accountability than transient conversation state.

The available description does not identify a particular Postgres schema, deployment model, retention policy, or memory format. It also does not explain whether the server creates database objects, expects an existing schema, or manages migrations. Those details should be confirmed from the project documentation before implementation.

How it works

The supplied information indicates that agent memory is persisted in Postgres and maintained with version information. Context can therefore be treated as portable rather than tied to one interaction, while permissions provide a stated control boundary around access. An audit trail is also part of the described design, indicating that memory-related activity is intended to be traceable.

OneDroid Engram MCP server is best evaluated for applications where multiple agent interactions need durable context and where operators care about access control or historical records. The material does not describe the exact request flow between an MCP client, the server, and Postgres, so tool invocation and synchronization behavior remain unspecified.

Tools and capabilities

The available description supports these capabilities:

• Store agent memory in the user's own Postgres database.
• Maintain versioned memory.
• Provide portable context for agents.
• Apply permissioned access to memory.
• Keep an audit trail.

No individual tool names, parameters, return values, search methods, update operations, or deletion operations are provided. Avoid assuming that the server exposes generic database queries or a particular memory-retrieval API without confirming the implementation.

Limitations and notes

The README was unavailable for this listing. As a result, the OneDroid Engram MCP server's installation process, required environment variables, transport, authentication setup, client compatibility, license, and operational requirements cannot be established from the supplied material. The listing also does not specify whether Postgres must be self-hosted, managed, or preconfigured beyond describing it as the user's own database.

Before adopting it, verify how permissions are defined, what events enter the audit trail, how versions are selected or restored, and how portable context is exported or consumed. Confirm the available MCP tools and their schemas as well. These checks are necessary to determine whether the implementation fits a particular agent runtime or database environment.