Read Everything in VS Code

VS Code's GitHub Copilot Agent mode can use remote MCP servers. VS Code's MCP configuration schema is different from Cursor's.

Public server URL: https://everything.emlynoregan.com/mcp/

Set up a workspace MCP server

1. Open your project in a current VS Code installation with an Agent-capable Copilot setup.
2. Create or edit .vscode/mcp.json in the project root.
3. Add Everything under the servers key. Keep existing servers when editing an established config:

{
  "servers": {
    "everything": {
      "type": "http",
      "url": "https://everything.emlynoregan.com/mcp/"
    }
  }
}

4. Save the file and use the VS Code MCP management controls to start or refresh the server if requested.
5. Open Copilot Chat, switch to Agent mode and enable everything in the tools picker.

For broader availability, use VS Code's user-level MCP settings rather than a workspace file. The steps above are intentionally project-scoped and do not write global configuration.

Test

Ask Copilot:

Call Everything's get_page MCP tool with path /beyond-the-application. Give me the page title and four main essays, using the returned page. Do not edit anything.

Successful discovery alone is not enough; verify a real get_page invocation and returned content.

What this connection provides

Everything is a remote public information source. It lets your VS Code agent read and search published articles, without requiring an Everything account or API key. Nothing needs to run locally.

If the MCP tool is connected but not used, select it in your agent's tools and ask explicitly for get_page. You can ask your assistant to compare articles and cite their original page links.

The two JSON formats above are alternatives, not files you must configure together. Follow VS Code's MCP guide for current client options.

All connection guides · First tests · Troubleshooting