Datapacks

A datapack is Meko's fundamental unit of isolation. Each datapack provides a self-contained persistent store for conversations, memory, and knowledge. MCP clients connect to the shared endpoint (https://mcp.mekodata.ai/mcp) and target a datapack by passing the datapack ID in tool calls.

What's in a datapack

When you create a datapack, Meko provisions isolated storage, scoped to your agent(s), and managed internally by Meko.

To connect an external MCP client (Cursor, Claude Code, and so on), you need:

• The MCP server URL, https://mcp.mekodata.ai/mcp (the same for every datapack and user).
• A user API key: a long-lived key you generate under Settings>API Keys in the portal (values start with mko_tkn_).

Agents select the datapack to connect to by passing the datapack_id inside each MCP tool call, not by using a different URL per datapack.

Create a datapack

The first time you sign in to the Meko portal, Meko walks you through the steps to create your default datapack (meko_default_datapack) and connect it to your client.

To create additional datapacks:

1. In the Meko portal, navigate to Datapacks.
2. Click Add Datapack.
3. Follow the instructions in the configure wizard.

Share a datapack

To share your datapack with colleagues:

1. In the Meko portal, under Datapacks, select the datapack you want to share.
2. Click Share.
3. Enter the email of the person you want to share with, and select the permission level.
4. Click Send Invite.

Isolation model

Each datapack is fully isolated:

• Data isolation. Logical isolation within a shared YugabyteDB universe. An authenticated user's clients can search that user's memories across agent namespaces, but can't read another datapack member's private memories.
• Credential isolation. User API keys and database credentials are scoped to your account; datapack data is separated in storage.
• MCP isolation. Tool calls include a datapack_id so the shared MCP server only reads and writes that datapack's data.

Connect via MCP

Each datapack exposes an MCP server that agents use to interact with their data.

When you create a datapack in the Meko portal, Meko provides instructions to connect your datapack to your agent automatically. The connection commands are also available under Connect in the Meko portal.

You can also configure clients by manually adding this configuration to your coding agent or agent framework. See Integrations.

Automatic capture and datapack pinning

When you have multiple datapacks, you designate one as your active pin - the default datapack where Meko saves conversations and memories. If you only have one datapack, Meko uses it automatically.

How to change your pin

Ask your agent in plain language:

Switch my Meko datapack to research

Or invoke the selector skill directly:

# Claude Code
/meko-agent-skills:meko-select-datapack

# Claude Desktop
/meko-select-datapack-desktop

The interactive selector will:

• List your accessible datapacks with your access role (such as, owner, maintainer)
• Let you pick by row number or datapack name (partial names work)
• Show your current pin with a checkmark
• Navigate multiple pages if you have many datapacks

To clear your pin and return to your account default, reply with clear or none.

Pins apply to new conversations only

When you switch pins: Your current conversation stays in its original datapack. The new pin takes effect only when you start a new chat. Existing conversations never move between datapacks.

Example: You're chatting in the "research" datapack. You say "Switch my pin to personal-projects." Meko updates the pin, but the current conversation keeps writing to "research." Your next chat will use "personal-projects."

How the pin persists across sessions

Claude Code: The pin is stored per project and survives restarting Claude Code, clearing your transcript, and opening another window in the same repository. Different projects can have different pins.

Claude Desktop: The pin is stored in Meko memory and survives across all Desktop conversations until you change or clear it.

If your pinned datapack is deleted or you lose access, Meko fails gracefully rather than silently writing elsewhere. Run the selector to pick an accessible datapack, or clear the pin.

Manage datapacks

Manage your datapacks from the Datapacks page in the Meko portal. Datapacks lists all your datapacks. From here you can add and share datapacks.

Select a datapack to view the conversations, memories, learnings, and knowledge the datapack holds.

From here, you can review and promote learnings to knowledge.