Connect VS Code

Before you start

This path is best suited to teams already using a VS Code MCP workflow, including GitHub Copilot Agent mode and other VS Code-based clients that support remote MCP from project configuration. An Enginy admin just needs to enable the MCP integration for the workspace — that’s it to get started. Enginy grants full access by default; restricting policy scopes is an optional, advanced step for later.

Add the hosted server

Add Enginy to .vscode/mcp.json:

{
  "servers": {
    "enginy": {
      "type": "http",
      "url": "https://openapi.enginy.ai/mcp"
    }
  }
}

Reload the MCP servers in VS Code and let it open the browser flow to approve Enginy.

Verify the connection

After authorization, ask the assistant to use Enginy MCP and run:

mcp_whoami

That confirms the hosted MCP server is reachable, OAuth completed, and the granted scopes match what Enginy approved.

Client support matrix

Compare support levels and setup shapes across every Enginy MCP client.

Security and troubleshooting

Debug auth, scope, token, and transport issues after VS Code connects.

Getting started

Clients

Guides

Reference

Before you start

Add the hosted server

Verify the connection

Client support matrix

Security and troubleshooting

​Before you start

​Add the hosted server

​Verify the connection

Client support matrix

Security and troubleshooting

Before you start

Add the hosted server

Verify the connection