Connect your agents

Integrate Meko with AI coding tools, agent frameworks, and consumer AI applications

Meko uses the Model Context Protocol (MCP) to connect each datapack to your AI coding tools, agent frameworks, and chat applications.

Follow these steps for any tool or framework:

  1. Create a datapack in the Meko web portal.
  2. Add the Meko MCP server to your AI agent or application.
  3. Use Meko through natural language prompts.

Quick start

In the Meko portal, select Connect and follow the steps.

The Installer method is recommended. It adds the Meko MCP server, plus agent skills and session hooks that make Meko automatic.

OAuth and a manual API key give your agent the Meko tools but not the skills, so it calls Meko only when you mention Meko in a prompt, such as "save this to Meko". For per-client configuration paths and installer options, see Connect to an AI agent.

Recommended. Adds the Meko MCP server, plus agent skills and session hooks that make Meko automatic.

In a terminal, run:

npx @yugabytedb/meko-mcp@latest --client <client> --url "https://mcp.mekodata.ai/mcp"

Replace <client> with claude-code, claude-desktop, cursor, codex, kiro, opencode, or all.

The installer opens your browser. Sign in the way you sign in to the portal, and it creates an API key for that client. Over SSH, add --no-browser and open the URL the installer prints. Restart your client if the Meko server doesn't show up. OpenCode always needs a restart.

On Claude Desktop the installer builds two .skill files that you import yourself. See Claude Desktop.

For Claude Desktop and other clients with a custom-connector flow. No installer and no API key.

  1. In your client, add a custom MCP connector pointing at https://mcp.mekodata.ai/mcp.
  2. Complete the OAuth handshake when the browser opens. Your Meko portal login is the identity.

For any MCP-compatible client, including VS Code.

  1. Go to Settings > API Keys and click Generate API key. Name it for the client that will use it (for example, laptop/cursor). The full key is shown once, so click Copy or Download .txt before closing.

  2. Add the Meko server to your client's MCP config. For example, in Cursor's mcp.json:

    {
  "mcpServers": {
    "meko": {
      "url": "https://mcp.mekodata.ai/mcp",
      "headers": {
        "Authorization": "Bearer <paste-your-api-key>",
        "User-Agent": "meko-mcp-installer/1.0"
      }
    }
  }
}

    Keep the Bearer prefix and the User-Agent header. Meko rejects requests without either.

  3. Restart your client.

To check the connection, ask your agent:

List my datapacks in Meko.

It calls the datapack_list tool and returns your datapacks, including the default one. If it doesn't, see Troubleshooting.

MCP server URL

Meko Cloud MCP clients such as Cursor, Claude Desktop, and Claude Code need the MCP server URL.

Every account and datapack connecting to Meko Cloud uses the same hosted endpoint URL:

https://mcp.mekodata.ai/mcp

The datapack Connect dialog also shows this URL. The URL doesn't change when you switch datapacks.

The datapack_id or datapack name in each MCP tool call selects the datapack.

Choose an authentication method

Meko Cloud accepts two ways for a client to authenticate.

API key OAuth
What the client sends An Authorization: Bearer header Nothing — it registers itself and opens a browser
Requires a browser No; works unattended and in CI Yes, whenever the session expires
Works from a terminal Yes No — see the note below
Identity The key you generated Your Meko portal login

Use only one method for each client. If you configure both, the client may use OAuth instead of your API key. OAuth uses your browser identity. If that identity doesn't have a Meko account, every call returns no Meko account found for your identity. Generating a new API key won't help; remove one of the two configurations.

OAuth

To use OAuth, enter only the MCP server URL. The client opens your browser so you can sign in to the Meko portal. It then gets the MCP tool list automatically.

API key

Meko API keys are long-lived personal access tokens. Each key starts with mko_tkn_.

Create a key in Settings > API Keys or in the datapack Connect dialog. To learn about naming, limits, revocation, and best practices, see API keys.

The datapack Connect dialog lists the prefixes of your active keys, such as mko_tkn_3KvL9X8z…. Use these prefixes to tell keys apart. When you configure a client, paste the full key that you saved, not the prefix.

Send the key as a Bearer token

To authenticate with an API key, add both headers:

Authorization: Bearer mko_tkn_your_key_here
User-Agent: meko-mcp-installer/1.0

The names matter. Meko reads only the Authorization header, and its value must start with Bearer . A header or environment variable named API_KEY, MEKO_API_KEY, or X-Api-Key doesn't work. Meko also rejects requests that don't include User-Agent.

Some clients need the mcp-remote helper to connect to a remote MCP server. In this guide, only Claude Desktop needs it. Its API key configuration is different; copy the Claude Desktop configuration.

Connect to an AI agent

Detailed instructions for your client.

Cursor Desktop

Cursor Web

Claude Desktop

Claude Code

Codex Desktop

Kiro IDE and CLI

OpenCode CLI and TUI

VS Code