# Connect Cursor, VS Code and other apps

> Connect Cursor, VS Code, GitHub Copilot or any remote MCP client to your FactorIn library with one URL and a sign-in in the browser.

Source: https://factor.in/docs/connect-other-apps/
Updated: September 30, 2026


Any app that supports remote MCP servers over HTTP and can run its own OAuth sign-in connects to your library with nothing but the URL. Cursor, VS Code, Windsurf, Goose, Cline and the rest all sign in from the browser on first use.

Connecting an AI app needs an active plan or a library inside its first 7 days.

## The URL

```
https://connect.factorin.com/mcp
```

Name the server `FactorIn` in your app's configuration. The name is the key the entry lands under, so it is the same string Claude Code and Codex write.

## Cursor

Cursor installs from a link its own client registers, so nothing is typed.

1. Open **Connected apps** in your FactorIn settings, pick the **Cursor** tab, and click **Add to Cursor**.
2. Click **Install** in Cursor when it opens.
3. Cursor opens your browser on first use. Approve the connection when FactorIn asks.

Adding it by hand instead: in Cursor's MCP settings, add an HTTP server named `FactorIn` with the URL above.

## VS Code and GitHub Copilot

VS Code reads the whole server entry out of a link. Copilot's MCP support is the same install, so there is nothing separate to do for it.

From a terminal, which also works for Insiders and remote windows where a link would land in the wrong installation:

```
code --add-mcp '{"name":"FactorIn","type":"http","url":"https://connect.factorin.com/mcp"}'
```

Confirm the install when VS Code opens. VS Code opens your browser on first use. Approve the connection when FactorIn asks.

## Claude Code and Codex

Both are covered on their own vendor's page: [Claude Code](https://factor.in/docs/connect-claude/index.md) and [Codex CLI](https://factor.in/docs/connect-chatgpt/index.md).

## Any other app

1. In any app that supports remote MCP servers, add the URL above as an HTTP server named `FactorIn`.
2. Sign in when the app opens your browser. FactorIn's authorization server supports dynamic client registration and loopback redirects, so a native client needs no pre-registered client id.
3. Ask the app to list your libraries to confirm it can see them.

If you are writing your own client: the connector publishes protected-resource metadata at `https://connect.factorin.com/.well-known/oauth-protected-resource/mcp` and authorization-server metadata at `https://factorin.com/.well-known/oauth-authorization-server`. The `resource` value is the connector URL exactly, compared byte for byte, and tokens are bound to it.

## Confirm it worked

Ask the app to list your libraries. Then paste the setup prompt from the Connected apps page. See [Set up your library](https://factor.in/docs/set-up-your-library/index.md).

## Disconnect

Open **Connected apps** in your FactorIn settings and revoke the connection. Removing the server from your app's configuration alone leaves the grant in place until you revoke it here.

## If it does not connect

- **The app cannot reach the server.** The URL has to match byte for byte: `https`, the host `connect.factorin.com`, the path `/mcp`, no trailing slash.
- **The sign-in page never appears.** The app has to open a browser for the OAuth sign-in. An app that cannot open one cannot connect.