Gingugu vs Agentram Mcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Gingugu vs Agentram Mcp
In-depth architectural comparison of the Gingugu and Agentram Mcp MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Gingugu
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Agentram Mcp
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Gingugu if you need specialized Knowledge & Memory tools running via a local process. Choose Agentram Mcp if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Gingugu when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Local SQLite storage with FTS5 full-text search, Hybrid retrieval combining BM25 and ONNX-based semantic embeddings, Typed memories with confidence lifecycle states (verified, inferred, stale, deprecated).
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Personal memory storage with agent ID and key, Shared namespaces for multi-agent memory collaboration, Text-based search across keys and values without embeddings.
Persistent memory for AI coding assistants. Local SQLite, no cloud. 16 MCP tools: store, recall, search, relate, consolidate, export, and credential vault (OS keychain). Typed memories with confidence lifecycle (verified/inferred/stale/deprecated), namespaces, knowledge graph, and hybrid BM25 + semantic search via fastembed ONNX. Works with Cursor, Windsurf, Claude, and any MCP client. pip install gingugu
Persistent memory for AI agents through a simple key-value HTTP API. No vector database or embeddings required. Store, retrieve, search, and share memory across agents with shared namespaces and TTL support. npx -y agentram-mcp
Category & Scope
Tools & Capabilities Breakdown
Gingugu Tools (6)
Local SQLite storage with FTS5 full-text search
Hybrid retrieval combining BM25 and ONNX-based semantic embeddings
Typed memories with confidence lifecycle states (verified, inferred, stale, deprecated)
Knowledge graph with typed relationships and namespaces
Credential vault integration using OS keychain
Supports multiple MCP clients and can run as a shared HTTP server
Agentram Mcp Tools (6)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Gingugu is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Agentram Mcp belongs to Knowledge & Memory using local stdio subprocess. Select Gingugu when you need capabilities focused on knowledge & memory and Agentram Mcp when you require tools for knowledge & memory.