What is the key difference between Keymem and Schedule Iii?

Keymem belongs to the Workplace & Productivity category with local stdio execution, while Schedule Iii belongs to the Workplace & Productivity category with cloud HTTP/SSE execution.

How do I install Keymem or Schedule Iii 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 Keymem and Schedule Iii free or paid?

Keymem operates under a Free / Open Source model (No auth required). Schedule Iii operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Keymem lists 12 tools with 2 views and 3 GitHub stars. Schedule Iii lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Keymem and Schedule Iii 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.

How do I install Keymem or Schedule Iii in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Keymem and Schedule Iii free to use, or do they require API keys?

Keymem is listed under a Free / Open Source model with No auth required . Schedule Iii operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Keymem and Schedule Iii at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both donggyun112-keymem and schedule-iii as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Keymem has a Quality Score of 65 /100 ( Great ) with 2 views, 0 installs, and 3 GitHub stars. Schedule Iii holds a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Keymem vs Schedule Iii

In-depth architectural comparison of the Keymem and Schedule Iii 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

Keymem

Workplace & Productivity · Local stdio

Quality: 65/100 (Great) | Auth: No auth required

Schedule Iii

Workplace & Productivity · Remote HTTP/SSE

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

Verdict Summary: Choose Keymem if you need specialized Workplace & Productivity tools running via a local process. Choose Schedule Iii if your workspace requires Workplace & Productivity integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Keymem when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: recall, browse_keys, read_key.

Explore Keymem Details

Choose Schedule Iii when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Schedule Iii Details

Feature & Specification Comparison

Specification	Keymem donggyun112 Workplace & Productivity	S Schedule Iii Workplace & Productivity
Summary	Associative key-graph memory for LLM agents — recall by association, not vector similarity.	Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out.
Category & Scope	Workplace & Productivity	Workplace & Productivity

Tools & Capabilities Breakdown

Keymem Tools (12)

recall

Search long-term memory for what is already known about the user, project, or topic — call this before your first reply and whenever the topic shifts. Always pass the active namespace when known. Returns matching key clusters only (not memory content): canonical concept, aliases, key type, match score, linked-memory count, hub status, and specificity. For a core lookup, complete read_key(key_id, original_query, namespace) then read_memory(memory_id, via_key_id, namespace): only the full read grows depth/access, reinforces the traversed edge, and learns aliases. Use short focused noun queries and decompose multi-fact questions into several recall calls. inject:true is only an unconfirmed passive preview and must not replace that traversal; injected memories are not reinforced. inject_top_k defaults to 1; inject_max_chars defaults to 2000 and marks truncated previews. An empty result returns {status:'no_match', nearest_keys} — the closest stored concepts below the gate; retry with one of those concepts when relevant.

browse_keys

Browse the vocabulary of one namespace when recall has no hit or you need an entry point. Returns active key clusters with hubs first, then by linked-memory count. This is index metadata only; continue with read_key(key_id, query, namespace) and read_memory(memory_id, via_key_id, namespace).

read_key

List the memories stored under one key (concept), ranked. Returns the canonical key, its aliases, and hub metadata plus ranked memory IDs and metadata — never memory content. Always pass the original focused query and active namespace when known: handles are then ranked by content relevance, which is essential for hubs. Call read_memory(memory_id, via_key_id=key_id, namespace) on the selected handle to confirm the fact and reinforce the path. Use limit/offset to page without flooding context.

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

Keymem Configuration

mcpServers (Claude Desktop / Cursor)

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

Schedule Iii Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "schedule-iii": {
      "url": "https://app.datavrn.com/agents"
    }
  }
}

Frequently Asked Questions

Keymem is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Schedule Iii belongs to Workplace & Productivity using remote streaming HTTP/SSE transport. Select Keymem when you need capabilities focused on workplace & productivity and Schedule Iii when you require tools for workplace & productivity.

More alternatives to Keymem More alternatives to Schedule Iii Workplace & Productivity category hub