What is the key difference between Memory and Tycana?

Memory belongs to the Knowledge & Memory category with local stdio execution, while Tycana belongs to the Knowledge & Memory category with local stdio execution.

How do I install Memory or Tycana in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Memory and Tycana free or paid?

Memory operates under a Free / Open Source model (No auth required). Tycana operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Memory lists 0 tools with 0 views and 0 GitHub stars. Tycana lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Memory and Tycana together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Memory vs Tycana

In-depth architectural comparison of the Memory and Tycana 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

Memory

Knowledge & Memory · Local stdio

Quality: 37/100 (Fair) | Auth: No auth required

Tycana

Knowledge & Memory · Local stdio

Quality: 37/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Tycana 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 Memory 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).

Explore Memory Details

Choose Tycana 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).

Explore Tycana Details

Feature & Specification Comparison

Specification	M Memory Knowledge & Memory	T Tycana Knowledge & Memory
Summary	Persistent memory for AI coding tools. 11 tools for any MCP-compatible AI tool.	Gives your AI assistant persistent memory and intelligence about your work patterns.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Memory Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Tycana Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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).

Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "memory-7": {
      "command": "npx",
      "args": [
        "-y",
        "@shackleai/memory-mcp@latest"
      ]
    }
  }
}

Tycana Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tycana": {
      "command": "npx",
      "args": [
        "-y",
        "tycana"
      ]
    }
  }
}

Frequently Asked Questions

Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Tycana belongs to Knowledge & Memory using local stdio subprocess. Select Memory when you need capabilities focused on knowledge & memory and Tycana when you require tools for knowledge & memory.

More alternatives to Memory More alternatives to Tycana Knowledge & Memory category hub