Meko for VS Code

Copilot’s agent mode can call tools, but its context ends with the workspace and the session. What it learned today is gone tomorrow, in VS Code and everywhere else.

Over MCP, Meko provides VS Code with:

Agent-scoped memory

What your agent learns persists beyond the session and is readable via every AI tool you connect to.

A shared knowledge base

Documents and promoted conclusions are searchable by all agents and teammates with access to the datapack.

A trace of every read and write

Each conversation is stored with its reasoning, so you can see what an agent did and why.

Your context outlives the editor

What Copilot’s agent learns is preserved in your datapack, readable from Cursor, Claude Code, or Codex, and shared with your team only when permitted.

Integration is one mcp.json entry, with an optional skill copy that teaches Copilot when to record and recall.

How Meko Benefits VS Code

Connect once, switch to agent mode, then ask, mentioning Meko so the agent calls the tools. Copy the skill in for automatic behavior.

Ask for last week’s context

“Check Meko: what did we decide about the auth flow?”

Copilot searches your memory before answering, instead of making you re-explain.

Save decisions as you code

“Remember in Meko that we pinned Node 20 for this service, and why.”

Stored with its reasoning, linked to the related context.

Keep your context when you switch editors

Memory lives in the datapack. A memory written from VS Code is readable from Cursor, Claude Code, or Codex.

Share the connection with the whole repo

Commit .vscode/mcp.json at the workspace root, so everyone who clones the project gets the same store.

Connecting Meko in VS Code

1. Sign in to GitHub Copilot in VS Code 1.99 or later, open Copilot Chat, and switch the mode to Agent. MCP tools appear in agent mode.

2. Add the server to .vscode/mcp.json at the workspace root. Use servers as the root key (Cursor and Claude Desktop use mcpServers), give the entry “type”: “http”, and pass your API key as a Bearer token. The inputs block makes VS Code prompt for the key once and store it securely, so nothing is hardcoded in the repo:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "meko-api-key",
      "description": "Meko API key",
      "password": true
    }
  ],
  "servers": {
    "meko": {
      "type": "http",
      "url": "https://mcp.mekodata.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${input:meko-api-key}",
        "User-Agent": "meko-vscode/1.0"
      }
    }
  }
}

Generate the API key in the Meko portal under Settings, then API Keys.

3. Run MCP: List Servers from the command palette to confirm it started.

4. To have Copilot record and recall without being told each time, copy the meko-mcp-tools skill to .github/skills/meko-mcp-tools/ for the project, or ~/.copilot/skills/meko-mcp-tools/ for every project.