Quick start
In this quick start you will:
- Connect your AI agent to a datapack.
- Add a document, and watch your agent answer from it.
- Tell your agent something once, then see a brand-new session recall it.
- Share the datapack with another agent on this computer, or with your team on Meko Cloud.
It takes about five minutes once Meko is running. Pick Meko Cloud or run Meko on your computer.
Connect your first agent
Cloud
You need the following:
- A Meko account. Sign up on the Free tier. See Meko pricing for plans.
- A supported client: Cursor, Claude Code, Claude Desktop, Codex, Kiro, or OpenCode.
- Node.js 20.18.1 or newer, to use the Meko installer.
Install using your agent
Use with Cursor, Claude Code, Claude Desktop, Codex, Kiro, OpenCode
For per-client configuration paths and other installation options, see Connect to an AI agent.
To check the connection, ask your agent:
List my datapacks in Meko.
It lists your meko_default_datapack, which was created for you automatically when you signed up. If it doesn't, see Troubleshooting.
Local
Meko on your computer is one binary: the server, a web UI, the MCP tools, and the REST API. No account needed. Linux (x64 or arm64) or macOS 14 or newer on Apple Silicon:
curl -fsSL https://mekodata.ai/install.sh | sh
The installer downloads the latest release, starts Meko, and leaves it running. It links meko and meko-cli into ~/.local/bin. Open a new terminal if your shell cannot find them.
meko status
Wait until the Context engine row shows ready. meko-cli fails until then. The first start creates a default datapack. meko ui opens the web UI at http://127.0.0.1:7777. It has no login. meko stop and meko start stop and start the server. The full command lists are meko and meko-cli.
meko agent list
meko agent connect claude
connect takes claude, codex, kiro, opencode, or cursor, and adds Meko for all of that agent's projects. With no name, it prints the MCP URL and token for any other client, including Claude Desktop:
meko agent connect
Start a new session of that agent. To check the connection, ask your agent:
List my datapacks in Meko.
It lists a datapack named default, which was created for you automatically when you started the server.