What is the key difference between Agent Memory and API Landing?

Agent Memory belongs to the Cloud Platforms category with local stdio execution, while API Landing belongs to the Cloud Platforms category with local stdio execution.

How do I install Agent Memory or API Landing 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 Agent Memory and API Landing free or paid?

Agent Memory operates under a Free / Open Source model (No auth required). API Landing operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Agent Memory lists 0 tools with 0 views and 0 GitHub stars. API Landing lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Agent Memory and API Landing 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

Agent Memory vs API Landing

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

Agent Memory

Cloud Platforms · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

API Landing

Cloud Platforms · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Agent Memory if you need specialized Cloud Platforms tools running via a local process. Choose API Landing if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Agent Memory when:

You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Agent Memory Details

Choose API Landing when:

You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore API Landing Details

Feature & Specification Comparison

Specification	Agent Memory Cloud Platforms	API Landing Cloud Platforms
Summary	Cloudflare Workers MCP server: agent-memory	Cloudflare Workers MCP server: api-landing
Category & Scope	Cloud Platforms	Cloud Platforms
Quality signal

Tools & Capabilities Breakdown

Agent Memory Tools (0)

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

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

Agent Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "agent-memory-4": {
      "command": "npx",
      "args": [
        "-y",
        "agent-memory-4"
      ]
    }
  }
}

API Landing Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Agent Memory is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, API Landing belongs to Cloud Platforms using local stdio subprocess. Select Agent Memory when you need capabilities focused on cloud platforms and API Landing when you require tools for cloud platforms.

More alternatives to Agent Memory More alternatives to API Landing Cloud Platforms category hub