GitHub Copilot & Codex

Copilot MCP / Instructions

Persistent Context & Rules for GitHub Copilot Chat

The Challenge Without Meto

GitHub Copilot often suggests outdated APIs, incorrect utility functions, or patterns that violate your repository conventions.

The Meto Solution

Meto generates both dynamic Copilot MCP configurations and concise .github/copilot-instructions.md files that anchor Copilot Chat to your verified standards.

Key Advantages with GitHub Copilot & Codex

Works in VS Code, JetBrains IDEs, and GitHub.com PR reviews

Enforces company or personal architectural guidelines

Dynamic MCP support in Copilot Chat preview channels

Eliminates hallucinated imports and incompatible packages

Step-by-Step Configuration Guide

Option A: Add .github/copilot-instructions.md

Create .github/copilot-instructions.md in your repository root and paste your Meto developer directives.

Option B: Configure Copilot MCP

In VS Code settings.json, add Meto under 'github.copilot.chat.mcpServers'.

.vscode/settings.json

{
  "github.copilot.chat.mcpServers": {
    "meto": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.metoctx.com/api/mcp/your-username",
        "--header",
        "Authorization: Bearer meto_mcp_your_personal_token"
      ]
    }
  }
}

Frequently Asked Questions

Does GitHub Copilot read .github/copilot-instructions.md automatically?

Yes! GitHub Copilot Chat natively reads .github/copilot-instructions.md in the current repository and includes it in every chat request context.

Ready to give GitHub Copilot & Codex persistent memory?

Create your Meto profile in 2 minutes. Fill in your stack once, and never repeat your setup again.

Get Started for Free All Integrations