# Connect Cursor to Zorlya

> Add the Zorlya MCP server to Cursor with one entry in mcp.json, then choose what Cursor may do on Zorlya's Connect page and sign in.

Source: https://zorlya.com/guides/ai-clients/cursor

Updated 2026-10-25.

To connect Cursor to Zorlya, add the address `https://mcp.zorlya.com` to `mcp.json` as a remote server, then approve access on Zorlya's Connect page when Cursor opens your browser. There is no API key, because Zorlya accepts OAuth sign in only.

## What you need

- An approved Zorlya account. A job seeker account needs the Pro plan, because AI client access is part of Pro.
- Cursor with MCP enabled.
- The server URL: `https://mcp.zorlya.com`

## Steps

1. Pick where the config lives. Cursor's docs name two files: `.cursor/mcp.json` in a project, or `~/.cursor/mcp.json` in your home directory for every project.
2. Add Zorlya under `mcpServers`. A remote server uses a `url` key:

```json
{
  "mcpServers": {
    "zorlya": {
      "url": "https://mcp.zorlya.com"
    }
  }
}
```

3. Save the file. Cursor's docs list a **Customize** area in the sidebar where you enable or disable servers, so turn Zorlya on there if it is off.
4. When Cursor starts the sign-in, a browser window opens on Zorlya's Connect page. It names Cursor, asks which of your Zorlya accounts Cursor should use, and asks for a permission level.
5. Choose a level and sign in. Read only is the default. Write tools, such as saving a job, appear only with Read and change. [What you approve when you connect](/guides/ai-clients/what-you-approve-when-you-connect) describes the steps.

Leave out `headers` and `auth`. Cursor's docs describe the static `auth` object (`CLIENT_ID`, `CLIENT_SECRET`, `scopes`) as the option for providers that do not support dynamic client registration. Zorlya does support it, at `/oauth/register`.

## What you should see

Zorlya appears in the server list with the tools of the account you chose. For a job seeker that is 15 read tools, plus 5 write tools with Read and change. Cursor keeps the connection for an hour per access token and refreshes it, and the refresh token lasts 30 days.

## Try it

- "Use Zorlya top_matches to list my five best open jobs and say why each one scored well."
- "Search Zorlya for remote senior backend roles with search_jobs, then compare the first two."

## If it does not connect

1. **The sign-in never opens or fails.** Cursor's docs say to open the Output panel (Cmd+Shift+U) and select "MCP Logs" to read connection and auth errors.
2. **Your account is not approved.** Zorlya's Connect page needs an approved account. See [security](/security) for how access works. A job seeker account on Free or Plus is also refused, because AI client access needs Pro.
3. **Your team blocks the server.** Cursor's docs mention an MCP allowlist under **Team Settings > MCP Configuration** for admins. If your team uses it, ask an admin to allow the server.

Cursor's redirect addresses are not a problem for Zorlya. Its docs list `https://www.cursor.com/agents/mcp/oauth/callback` and, for the desktop app, `http://localhost:8787/callback`. Both are in Zorlya's list for Cursor.

## What we checked

The steps come from Cursor's documentation, read on 2026-10-17. We did not try the connection to Zorlya in Cursor. The docs do not show a complete example of a remote server using only OAuth, so the config above is the documented `url` form with the Zorlya address filled in.

For the server side, see [developers](/developers).

## Sources

- https://cursor.com/docs/context/mcp