Log inSubmit server

Agenticmemory vs IWE

A side-by-side look at the Agenticmemory and IWE MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Agenticmemory logoAgenticmemoryKnowledge & Memory · Remote HTTP/SSEPersistent memory for AI agents — history, context, semantic search, queues. 17 tools, stdio/SSE.39FairAuth: not declaredIWE logoIWEKnowledge & MemoryMarkdown knowledge base as agent memory. Runs against the notes directory it is started in.44FairAuth: no auth required

Verdict: choose Agenticmemory for knowledge & memory work over a hosted endpoint; choose IWE for knowledge & memory. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Agenticmemory logoChoose Agenticmemory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: AGMRY_API_KEY, AGENTICMEMORY_API_KEY, AGMRY_ENCRYPTION_KEY.
Explore Agenticmemory

IWE logoChoose IWE when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • Its auth model fits you: No auth required.
Explore IWE

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgenticmemory logoAgenticmemoryIWE logoIWE
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal39/100 · Fair44/100 · Fair
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsAGMRY_API_KEYAGENTICMEMORY_API_KEYAGMRY_ENCRYPTION_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars11,790
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Agenticmemory View IWE

Tools & capabilities

Agenticmemory tools

No tool names declared yet. Check the project README from the listing page.

IWE tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Agenticmemory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agenticmemory": {
      "url": "https://mcp.agenticmemory.ai/sse"
    }
  }
}

IWE

No confirmed install command for IWE yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Agenticmemory is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. IWE belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Agenticmemory for knowledge & memory work and IWE for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. IWE has no confirmed install command yet — follow its own setup instructions.

Agenticmemory has no declared pricing — check the project's own site. IWE is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add agenticmemory and iwe as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Agenticmemory has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. IWE has 44/100 (Fair) with 2 views, 0 installs and 1,790 GitHub stars.

Popular comparisons with Agenticmemory

Popular comparisons with IWE