# Connect Prior to Cursor and VS Code

> Add Prior to Cursor or VS Code with one button, a command or a config file, sign in once, then manage your tasks without leaving your editor.

Source: https://priortasks.com/docs/integrations/connect-cursor-and-vs-code/
Last updated: 2026-11-05

Both editors can use Prior's tools from their AI chat. You can ask for the next task to work on, create a task from a TODO comment you wrote a moment ago, or close a task when the work is done. Each editor asks before it runs a tool, by default.

## Add it with a button

Server address: https://api.priortasks.com/mcp

Click **Add to Cursor** or **Add to VS Code**. The button opens the editor's install page, which opens the editor with Prior filled in. Review what it shows and confirm. The first time the editor uses Prior, your browser opens so you can sign in and click **Allow**.

## Cursor by hand

Add Prior to a file named `mcp.json`: `.cursor/mcp.json` in a project, or `~/.cursor/mcp.json` in your home folder to have it in every project.

```json
{
  "mcpServers": {
    "prior": {
      "url": "https://api.priortasks.com/mcp"
    }
  }
}
```

Cursor signs in with OAuth when a server asks for it. You manage and turn servers on or off from **Customize** in the sidebar. By default Cursor asks for approval before it uses an MCP tool: click the arrow next to the tool name to see what it will send. Cursor documents this in [Model Context Protocol (MCP)](https://cursor.com/docs/mcp).

## VS Code by hand

VS Code reads MCP servers from `.vscode/mcp.json` in a workspace, or from your user profile. The format uses `servers`:

```json
{
  "servers": {
    "prior": {
      "type": "http",
      "url": "https://api.priortasks.com/mcp"
    }
  }
}
```

You can also add it from a terminal:

```
code --add-mcp '{"name":"prior","type":"http","url":"https://api.priortasks.com/mcp"}'
```

Or open the Command Palette (<kbd>Cmd</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>), run **MCP: Add Server**, and choose HTTP. **MCP: List Servers** shows each server and lets you start it, sign in and read its output.

VS Code tries Dynamic Client Registration first for sign-in, which Prior supports. Its menus for MCP change between releases, so search "MCP" in the Command Palette if a name differs. VS Code documents this in [MCP servers](https://code.visualstudio.com/docs/copilot/customization/mcp-servers) and the [MCP developer guide](https://code.visualstudio.com/docs/copilot/guides/mcp-developer-guide).

## Use it

In the editor's AI chat, ask in plain words: "What should I work on next in the Website launch project?", "Add a task to fix the login redirect, priority 2, due Friday", "Mark the invoice export task as done".

Prior's prompts, such as `plan_my_day`, show up where your editor lists MCP prompts, if it supports them. See [Every tool and prompt](https://priortasks.com/docs/integrations/mcp-tools/).

## Good to know

- **Transport.** Prior uses Streamable HTTP, which both editors support. An editor that only speaks the older SSE transport cannot connect.
- **Keep approvals on.** Approve a tool only when you understand what it will change. See [Keep your connection safe](https://priortasks.com/docs/integrations/mcp-security/).
- **One setup, every project.** Add Prior at the user level (`~/.cursor/mcp.json`, or your VS Code user profile) to have it everywhere, or in the project to share the setup with your team. The file holds no secret, because sign-in is done by each person.
- **Disconnect** from **Settings → Integrations** with **Revoke**, and remove the entry from the file.