# Connect Cursor to Workspace369

> Add the Workspace369 MCP server to Cursor with mcp.json, sign in, and have Cursor's agent set up your CRM or build a custom front end on your workspace data.

- Product: Workspace369
- Documentation version: 2026.3
- Section: AI connections
- Last updated: 2026-11-02
- Canonical source: https://docs.workspace369.com/v/2026.3/ai-connections/connect-cursor-to-workspace369/

---

Cursor connects to Workspace369 through the Workspace369 MCP server. Once connected, Cursor's agent can read and update your clients, pipeline, follow-ups, proposals, invoices and tasks while you code, always within your own permissions. That makes it a quick way to build a custom CRM front end on real workspace data.

No workspace yet? [Start a free trial](https://app.workspace369.com/signup?utm_source=docs-connect-cursor-to-workspace369&utm_medium=docs_page&utm_campaign=ai-builders-crm&next=ai-connections). Then make sure **Allow AI connections** is on under **Settings → AI → AI connections**.

## Choose the server URL

| URL | What Cursor gets |
| --- | --- |
| `https://mcp.workspace369.com/mcp/crm` | The core CRM tools, with nothing that sends to a client. A good fit for building and testing an app. See [Connect the core CRM toolset](/v/2026.3/ai-connections/connect-the-core-crm-toolset/). |
| `https://mcp.workspace369.com/mcp` | Every Workspace369 tool, including inbox, calendar and sends that wait for your approval. |

## Add the server

Cursor reads MCP servers from `mcp.json`. Use `.cursor/mcp.json` in your project to connect only that project, or `~/.cursor/mcp.json` to connect every project.

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

<!-- Source: https://cursor.com/docs/context/mcp (mcp.json locations, url servers, OAuth with PKCE and dynamic client registration, Customize toggle, MCP Logs; checked 2026-11-02). -->

Leave out `headers`. With no key in the file, Workspace369 asks you to sign in instead, so no secret ends up in your project.

## Sign in

When Cursor connects, Workspace369 asks you to sign in and Cursor opens the sign-in page in your browser.

1. Sign in with Google or your Workspace369 email and password.
2. Under **Choose a workspace**, pick the workspace.
3. Review the permissions and choose **Approve access**.

The steps are the same as for every app: see [Approve the connection](/v/2026.3/ai-connections/connect-an-ai-app-to-your-workspace/#approve-the-connection). Your MCP servers are listed under **Customize** in Cursor's sidebar, each with an on/off toggle. If Cursor asks you to sign in later, use the server's entry there.

A script or CI job that can't open a browser uses a [personal access token](/v/2026.3/ai-connections/personal-access-tokens/) in `headers` instead. [Connect the core CRM toolset](/v/2026.3/ai-connections/connect-the-core-crm-toolset/) shows that setup for Cursor.

## Set up your CRM, then build on it

In a new workspace, ask Cursor's agent to use the **set_up_my_crm** prompt, or say: "Set up my CRM in Workspace369 for my business." It proposes pipeline stages and client fields, shows a preview, and writes nothing until you say yes.

Then try:

- "Use the build_crm_frontend prompt to build a client list and pipeline board on my Workspace369 data."
- "Import my clients from clients.csv." (the **import_my_clients** prompt)
- "Who should I follow up with today?"

Want a head start on the code? [Build a CRM with AI](https://workspace369.com/build-a-crm-with-ai/?utm_source=docs&utm_medium=referral&utm_campaign=ai-builders-crm&utm_content=connect-cursor-to-workspace369) has a ready build prompt for coding agents such as Cursor.

## Turn off or remove the connection

To pause it, turn the server off in **Customize**; a disabled server doesn't load or appear in chat. To remove it, delete the `workspace369` entry from `mcp.json`. To end access from the Workspace369 side, open **Settings → AI → AI connections**, find the Cursor entry under **Your AI apps** in **Your connections**, and choose **Disconnect**.

If the connection fails, open Cursor's Output panel and choose **MCP Logs**, then see [Fix AI app connection problems](/v/2026.3/ai-connections/fix-ai-app-connection-problems/).