--- title: "Universal connectivity" url: "https://docs.mekodata.ai/use-meko/connect/" --- # Universal connectivity Integrate Meko with AI coding tools, agent frameworks, and consumer AI applications Connect Meko to your tools and frameworks Meko uses the Model Context Protocol (MCP) to connect each datapack to your AI coding tools, agent frameworks, and chat applications. Meko Cloud Free tier MCP tool usage counts toward Meko Cloud Free tier limits, including **1,000 conversation messages** and **10,000 retrieval requests** per month (memory and knowledge-base searches). See [Meko pricing](https://mekodata.ai/pricing/) for plan details. Meko Local The following instructions apply to Meko Cloud. For information on installing and connecting Meko Local on your computer, see [meko Install](/reference/meko/#install). 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](/use-meko/connect/connect-to-ai-agent/). - Client Installer - Connector (OAuth) - Manual MCP Install #### Client Installer *Recommended. Adds the Meko MCP server, plus agent skills and session hooks that make Meko automatic.* In a terminal, run: ```sh npx @yugabytedb/meko-mcp@latest --client --url "https://mcp.mekodata.ai/mcp" ``` Replace `` 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](/use-meko/connect/connect-to-ai-agent/#claude-desktop). #### Connector (OAuth) *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. OAuth doesn't work for every client Clients that complete OAuth through a local `http://127.0.0.1` callback currently fail with an HTML `403 Forbidden`. That covers command-line clients and some IDEs. Use the installer or an API key for those. Hosted connectors with an `https` callback, such as Claude Desktop's, are unaffected. #### Manual MCP Install *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`: ```json { "mcpServers": { "meko": { "url": "https://mcp.mekodata.ai/mcp", "headers": { "Authorization": "Bearer ", "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: ```text 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](/troubleshooting/#common-problems-installing-and-connecting). ## 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: ```text 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`](#send-the-key-as-a-bearer-token) 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. OAuth not supported from the command line Clients that register a local `http://127.0.0.1` callback receive an HTML `403 Forbidden` error. This includes command-line clients and Kiro IDE. Use an API key for those clients. Claude Desktop's custom connector uses a supported callback and can use OAuth. ### 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](/use-meko/api-keys/). Warning Meko cannot show the full API key again after you close the create dialog. If you lose it, revoke the old key and generate a new one. 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: ```text 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](/use-meko/connect/connect-to-ai-agent/#claude-desktop). ## Connect to an AI agent Detailed instructions for your client. [![Cursor Desktop](/logos/integrations/cursor.svg) \ **Cursor Desktop**](/use-meko/connect/connect-to-ai-agent/#cursor-desktop) [![Cursor Web](/logos/integrations/cursor.svg) \ **Cursor Web**](/use-meko/connect/connect-to-ai-agent/#cursor-web) [![Claude Desktop](/logos/integrations/claude.svg) \ **Claude Desktop**](/use-meko/connect/connect-to-ai-agent/#claude-desktop) [![Claude Code](/logos/integrations/claude.svg) \ **Claude Code**](/use-meko/connect/connect-to-ai-agent/#claude-code) [![Codex Desktop](/logos/integrations/codex.svg) \ **Codex Desktop**](/use-meko/connect/connect-to-ai-agent/#open-ai-codex-desktop) [**Kiro IDE and CLI**](/use-meko/connect/connect-to-ai-agent/#kiro-ide-and-cli) [**OpenCode CLI and TUI**](/use-meko/connect/connect-to-ai-agent/#opencode-cli-and-tui) [![VS Code](/logos/integrations/vscode.svg) \ **VS Code**](/use-meko/connect/connect-to-ai-agent/#vs-code)