v2.0.0 — July 17, 2026

This release covers the @yugabytedb/meko-mcp installer, the Meko MCP server, and the Claude Code, Claude Desktop, Cursor, and Codex agent skills — the pieces you get from the Automated install flow and the MCP server reference.

New Features

MCP Server

• Implicit memory extraction — the marquee change in this release. Posting a substantive conversation turn (via automatic capture or an explicit conversation_add_message) now gives Meko what it needs to build durable memory on its own, asynchronously. See Work with memory.
• Artifact storage — artifact_put and artifact_get add MCP-native storage and retrieval for files an agent generates (reports, CSVs, code output) for later or cross-agent access.
• Datapack-aware automatic capture — automatic capture (Claude Code hooks, Claude Desktop skill) now writes to your pinned datapack instead of always falling back to the account default. See Automatic capture and datapack pinning.

Integrations

• Claude Desktop datapack selector — pick, switch, or clear which datapack automatic capture writes to, without leaving the chat.

Improvements

Integrations

• More reliable Claude Desktop capture — the Desktop skill now presents Meko as your memory/knowledge/observability system of record, which meaningfully improves proactive capture on cautious models when paired with the documented Instructions for Claude snippet. See Troubleshooting.
• Codex and Cursor install stability — hooks and skills installed by the npm installer now copy into a stable, home-directory-owned location instead of pointing back into an ephemeral npx cache, so they survive npx cache eviction.

Bug Fixes

Integrations

• Requests blocked by Cloud's WAF — installer-generated configs for every supported client (Claude Code, Cursor, Claude Desktop, the Desktop Extension, Codex) now send an explicit User-Agent header, fixing intermittent 403 responses.
• Claude Desktop Extension bearer token truncation — the .mcpb launcher no longer lets shell parsing split the Authorization: Bearer <token> header, which had been silently dropping the token.

Changes

MCP Server

• Breaking: memory capture doctrine — agents should post substantive turns with conversation_add_message instead of calling memory_add for every stated fact; extraction now happens automatically from posted turns. Explicit memory_add is still the right tool for direct "remember this" requests, facts that only exist in an assistant's or tool's output, and corrections that must supersede an already-extracted fact.
• flush_pending_memory_candidates deprecated — kept for one release for backward compatibility; use automatic capture or conversation_add_message instead. See the MCP server reference.

Known limitations

• contextual_prominence_search is disabled on Meko Cloud — it's listed in the tool surface for forward reference, but an authenticated call currently returns feature_disabled. Use conversation_search, memory_search, and knowledgebase_search individually instead.
• Claude Desktop automatic capture is model-dependent — Sonnet- and Opus-class models need the Instructions for Claude snippet to capture proactively; hookless Desktop capture remains best-effort even with it.
• Automatic extraction is best-effort — it can occasionally miss an individual fact within a saved turn. Use explicit memory_add for anything that must not be lost.
• A datapack pin change doesn't move your current conversation — a conversation can't switch datapacks after it's created, so a pin change takes effect starting with your next new session.

Install or upgrade

npx @yugabytedb/meko-mcp@2.0.0