Integrations
Meko uses the Model Context Protocol (MCP) to connect each datapack to your AI coding tools, agent frameworks, and chat applications.
MCP tool usage counts toward Free tier limits, including 1,000 conversation messages and 10,000 retrieval requests per month (memory and knowledge-base searches). See Meko pricing for plan details.
Follow these steps for any tool or framework:
- Create a datapack in the Meko web portal.
- Add the Meko MCP server to your AI agent or application.
- Use Meko through natural language prompts.
MCP server URL
MCP clients such as Cursor, Claude Desktop, and Claude Code need the MCP server URL.
Every account and datapack 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 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.
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.
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:
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.
