v2.5.1 - October 28, 2026

Release notes for installer and public skills plugin v2.5.1 - a local Meko URL uses your API key, and the skills say when to upload a file.

This release covers version 2.5.1 of the @yugabytedb/meko-mcp installer and the public Meko agent skills plugin.

Published skill versions: meko-mcp-tools 3.5.0, meko-mcp-tools-desktop 2.12.0, meko-select-datapack 1.2.1, meko-select-datapack-desktop 1.3.1, and Kiro power 1.3.0.

Install or upgrade

npx @yugabytedb/meko-mcp@2.5.1

To send a key you already have to a local Meko, set MEKO_API_KEY and pass the URL. Replace <paste-your-api-key> with your key. --yes skips the prompts.

MEKO_API_KEY=<paste-your-api-key> npx @yugabytedb/meko-mcp@2.5.1 --url http://127.0.0.1:7778/mcp --yes

Claude Desktop can also install the MCP server from meko-2.5.1.mcpb. That file installs the MCP server only. It still asks you to paste an API key, and it doesn't install the Desktop skills. See Claude Desktop.

Claude Code users can also update the skills plugin directly. That update installs the new upload guidance. Rerun the installer when you need the local API key fix.

The public plugin source is in yugabyte/meko-skills.

Changes

Fixes

  • Send MEKO_API_KEY to a local Meko - If you don't pass --api-key, the installer uses MEKO_API_KEY for every URL, including a local Meko such as http://127.0.0.1:7778/mcp. The client config includes Authorization: Bearer and that key. A local install on 2.5.0 left the header out, and calls returned 401. --api-key overrides MEKO_API_KEY. Browser sign-in still runs only for a Cloud URL. With no key at all, a local install still writes no Authorization header.
  • --local stays keyless - --local uses http://localhost:8000/mcp and ignores MEKO_API_KEY. A --yes run that reuses a saved http://localhost:8000/mcp entry does too. Pass that address with --url when you want the variable applied.
  • Install and --migrate use the same URL check - A URL is local when its hostname is localhost, ::1, or an address in 127.0.0.0/8. Any other hostname is Cloud, including localhost.example.com. Browser sign-in can create the key, and a run with no terminal still requires a key. --migrate uses the same check, so install and migration accept the same URLs.

Improvements

  • Choose a knowledge-base file or an artifact - Ask the agent to add a file. It uploads the file to the knowledge base when you want to search inside it, and saves an artifact when you need the file back whole. It asks which one you want only when that isn't clear. It still names the file and the datapack and waits for a yes before it uploads, because the file goes into the shared knowledge base. An agent that can't send the file itself, such as Claude Desktop without a code tool, doesn't call knowledgebase_upload_document. This is in meko-mcp-tools 3.5.0, meko-mcp-tools-desktop 2.12.0, and Kiro power 1.3.0. See Where to store it and Upload from your agent.

Known limitations

  • OpenCode support covers CLI and TUI 1.18.x. It doesn't cover OpenCode Desktop, V2 preview APIs, headless or remote sessions, or child-session migration.
  • OpenCode capture stores visible user text and the first visible assistant message. It doesn't store tool calls, hidden reasoning, files, attachments, or streaming output. It uses your account's default datapack and doesn't read the pin. --datapack applies to --migrate only.
  • Browser sign-in needs a terminal. The Desktop extension (meko-2.5.1.mcpb) does not create a key.
  • The Connect dialog command still includes --api-key <paste-your-api-key>.
  • Claude Desktop has no session hooks, so automatic capture still depends on the model even with the skills installed.