> For the complete documentation index, see [llms.txt](https://developer.frontitude.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.frontitude.com/mcp/connecting/cursor.md).

# Cursor

1. Open the ***AI tools*** card on your [workspace integrations page](https://app.frontitude.com/settings/integrations?utm_source=mcp-docs), choose ***Cursor***, then click ***Add to Cursor***. Cursor opens and asks you to confirm.
2. Sign in. Cursor sends you to Frontitude to finish. Pick your workspace, then choose which tools Cursor may use.

## If nothing happens

Cursor isn't installed on this computer, or your browser blocked the link.

1. Open `~/.cursor/mcp.json`, and create the file if it isn't there yet:

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

   If the file already has servers in it, add the `frontitude` entry to the `mcpServers` block rather than replacing the file.
2. Save the file and restart Cursor. Cursor then sends you to Frontitude to sign in.

Either way, ask Cursor which Frontitude workspace it's connected to. It should name yours.

For more information, see [Cursor's MCP documentation](https://docs.cursor.com/en/context/mcp).

{% content-ref url="/pages/zHZv4GJ2vmDPJLqHJ72q" %}
[Examples](/mcp/examples.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.frontitude.com/mcp/connecting/cursor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.