Memory MCP server
Persistent memory using a local knowledge graph to retain information across conversations. Connect your AI agents to Memory with enterprise-grade governance, observability, and control through Mintive Gateway.
Tools included with Memory MCP
create_entities
Create multiple new entities in the knowledge graph
create_relations
Create multiple new relations between entities in the knowledge graph. Relations should be in active voice
add_observations
Add new observations to existing entities in the knowledge graph
delete_entities
Delete multiple entities and their associated relations from the knowledge graph
delete_observations
Delete specific observations from entities in the knowledge graph
delete_relations
Delete multiple relations from the knowledge graph
read_graph
Read the entire knowledge graph
search_nodes
Search for nodes in the knowledge graph based on a query
open_nodes
Open specific nodes in the knowledge graph by their names
Works with every major client
Why Mintive gateway
Centralized governance
One-click deployment
OAuth + SSO enforcement
Host stdio servers on Mint instead of running locally
Observability and control
Enterprise hardening
Supports shared and per-user auth
Granular tool access control
FAQs
Yes. Mintive Gateway is SOC 2 compliant and uses OAuth-based authentication for all Memory MCP interactions.
ChatGPT, Claude, Claude Code, and any MCP-compatible client.
Schedule a demo to receive Mintive Gateway credentials and configuration details for connecting your AI client to the Memory MCP Server.
The Model Context Protocol (MCP) is an open standard that lets AI models connect to external tools and data sources through a single, secure interface—the "USB-C for AI."
Access is managed centrally in Mintive Gateway. Administrators can grant, suspend, or revoke connections and control authentication through identity-based policies.
Mint provides usage dashboards and audit logs for monitoring authentication, tool invocations, and connection activity.
No. Mint supports OAuth authentication and delegated token marshalling, allowing secure, automatic credential handling without manual entry.
Yes. Integrate Mint with Okta or another identity provider to enable role-based access. Map teams or groups to Virtual MCPs (VMCPs) for structured permissions.
Yes. Teams can define VMCPs with custom tool prompts, configurations, and behavior tailored to their workflows.
Yes. You can bring your own MCP servers and manage them through Mint with governance and security controls.
Create a Mintive app in Okta, upload the metadata XML, map groups to roles, and verify the connection.
Mint detects and notifies administrators of changes to tool definitions and descriptions, including new tools, renamed tools, removals, and updates to metadata.
Yes. Each invocation is logged with timestamp, user identity, and client metadata for traceable auditing.