Guides / Connect an AI client

Connect VS Code with GitHub Copilot to Zorlya

Add Zorlya as an HTTP MCP server in VS Code so Copilot's agent can read your matches, then sign in on Zorlya's Connect page.

3 min read. Updated .

To connect VS Code with GitHub Copilot to Zorlya, add an HTTP server with the address https://mcp.zorlya.com in .vscode/mcp.json, then sign in on Zorlya’s Connect page. VS Code is not on Zorlya’s list of AI apps, so registration may be refused. We have not tried it.

Not on Zorlya’s list yet. Zorlya accepts only the AI apps on its list: Claude, ChatGPT, Claude Code and Cursor (how it works). VS Code is not on it, so Zorlya refuses its registration unless VS Code sends you back to an address that a listed app uses. We have not tried it. The steps below are what VS Code’s own documentation describes for a remote server.

What you need

  • An approved Zorlya account. A job seeker account needs the Pro plan, because AI client access is part of Pro.
  • VS Code with GitHub Copilot chat.
  • The server URL: https://mcp.zorlya.com

Steps

  1. Open the guided flow. VS Code’s docs say to run Chat: Open Customizations from the Command Palette, select MCP Servers, then select Add Server. The same flow is available as MCP: Add Server.
  2. Select HTTP, which the docs describe as the choice for a “remote HTTP or Server-Sent Events (SSE) server”.
  3. Enter https://mcp.zorlya.com as the URL.
  4. Give the server an ID, for example zorlya, and pick the configuration file.
  5. Or write the file yourself. In .vscode/mcp.json the top-level key is servers:
{
  "servers": {
    "zorlya": {
      "type": "http",
      "url": "https://mcp.zorlya.com"
    }
  }
}
  1. Start the server. Servers in a trusted workspace start without a separate prompt. Otherwise VS Code shows a trust dialog the first time.
  2. When your browser opens on Zorlya’s Connect page, choose the account and the permission level, then sign in. Read only is the default. Write tools appear only with Read and change.

Do not add an oauth block. VS Code’s reference describes it as an optional object that needs a clientId, for servers where you already hold a client ID. Zorlya has no fixed client ID to give you, because clients register themselves at /oauth/register, and only the AI apps on Zorlya’s list can.

What you should see

MCP: List Servers shows Zorlya running. Select Configure Tools in the chat input to switch individual tools on or off. For a job seeker account you should see 15 read tools, plus 5 write tools with Read and change.

Try it

  • “Call Zorlya top_matches and summarize my best five jobs in a table.”
  • “Use search_jobs to find hybrid data roles, then track_application on the one I pick.” This second step needs Read and change.

If it does not connect

  1. VS Code never starts the sign-in. VS Code’s docs do not describe the Zorlya case, so check MCP: List Servers and the server’s output for the error.
  2. Your organization restricts MCP. The docs say organizations can manage MCP access through Copilot enterprise-managed settings and an allowlist. Ask your admin.
  3. The redirect. VS Code’s extension guide says an identity provider’s redirect list must include http://127.0.0.1:33418 and https://vscode.dev/redirect. Neither is in Zorlya’s list of return addresses, so registration is refused.

What we checked

The steps come from VS Code’s documentation, read on 2026-10-17. We did not try the connection to Zorlya in VS Code. The docs we read do not say which Copilot plans or settings are needed for MCP, so check your own.

More on the server: developers.

Sources