GitHub · Coding agents

Memrio for GitHub Copilot in VS Code

Copilot agent mode discovers MCP servers from .vscode/mcp.json. Add the registry with a prompted secret, commit the file, and every contributor’s Copilot reads the same approved engineering knowledge.

Jump to setup
live
VS Code Copilotmemrio

Why pair them

01

Commit the config, not the key

VS Code prompts each developer for the key once and stores it securely.

02

Works in agent mode

Copilot lists browse, search_pages, and get_page as tools it can call while it works.

03

Governed source

The team edits pages in the registry; Copilot only reads what a reviewer published.

Setup

3 steps, about ten minutes.

You need two values from an agent page in Memrio: the workspace MCP URL and an API key. Examples use https://memrio.ai/api/mcp/acme — swap in yours.

Create an agent and key first
  1. 01

    Create .vscode/mcp.json

    Use an input so the key is prompted instead of committed.

    .vscode/mcp.json
    {
      "inputs": [
        {
          "type": "promptString",
          "id": "memrio-key",
          "description": "Memrio agent API key",
          "password": true
        }
      ],
      "servers": {
        "memrio": {
          "type": "http",
          "url": "https://memrio.ai/api/mcp/acme",
          "headers": {
            "Authorization": "Bearer ${input:memrio-key}"
          }
        }
      }
    }
  2. 02

    Start the server

    Open the file and click Start above the server entry, or run MCP: List Servers from the command palette. Paste the key when prompted.

  3. 03

    Use it in Copilot Chat

    Switch Copilot Chat to Agent mode. The registry tools appear under the tools picker. Ask a question and Copilot browses the page set first.

Try it

A first prompt for VS Code Copilot

Use the memrio tools to find our logging standards, then update this service to follow them.

FAQ

VS Code Copilot and Memrio

Does VS Code support HTTP MCP servers?
Yes. Set "type": "http" with a url and optional headers in .vscode/mcp.json. Inputs let you prompt for secrets instead of committing them.
Does Memrio need a workspace or page-set header?
No. The API key is scoped to one workspace and one agent page set, so the key alone tells the server what the agent may read. Send only the Authorization header.
Which pages can the agent see?
Only published pages inside the agent page set you configured. Drafts and pages waiting on review are hidden unless you turn on "Read drafts" for a test agent.
Can the agent edit pages?
Only if you enable "Can edit pages" on that agent. It then gets get_page_source, create_page, update_page, and append_to_page. Edits are submitted as versions for human review unless the agent is also allowed to publish.

Other integrations