> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/mcp-server/deployment-options/remote-mcp/remote-oauth-mcp/set-up-cursor-using-remote-oauth.md).

# Set up Cursor using Remote OAuth

## Scenario

An organization has deployed the OvalEdge Remote MCP Server with OAuth authentication and wants to enable developers or business users to securely access governed metadata from the Cursor AI editor. This procedure explains how to configure the Remote MCP Server in Cursor, authenticate using OAuth through Okta, and verify that the MCP server is successfully connected and ready to process natural language requests.

This integrates seamlessly with the procedure I provided earlier and maintains the same documentation style used throughout your help center.

### Steps Involved

1. Open the **Cursor** application.
2. Click the **Settings** (⚙️) icon in the upper-right corner.

   ![](https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2FN8H9yQcr4sVUe7YU8h01%2Funknown.png?alt=media\&token=9a13fd60-e097-46e0-bb51-135ee93074f9)
3. In the left navigation pane, click **Tools & MCPs**.

   ![](https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2F4FqJ2oaJGmI2nxEzZUZn%2Funknown.png?alt=media\&token=8a3dfa62-219d-42e5-bfd4-2c8a491e0a6e)
4. Under **Installed MCP Servers**, click **New MCP Server**.
5. Open the **mcp.json** configuration file. Under the mcpServers section, add a new entry for the OvalEdge Remote MCP Server.<br>

   ```json
   {
     "mcpServers": {
       "playwright": {
         "command": "npx",
         "args": [
           "@playwright/mcp@latest"
         ]
       },
       "ovaledge-remote-oauth": {
         "url": "https://YOUR_PUBLIC_MCP_BASE_URL/mcp"
       }
     }
   }
   ```
6. Specify the **url** parameter with the Remote MCP Server endpoint provided by the administrator. Save the **mcp.json** file.

   ![](https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2FJYzfCngN1ycS2A2mZPsI%2Funknown.png?alt=media\&token=33795799-bf21-43e5-8ca5-b7dd4440223a)
7. Return to the **Tools & MCPs** page.
8. Verify that the newly added OvalEdge Remote MCP Server appears under **Installed MCP Servers**.

   ![](https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2F9ohCqN3CwqGTCn9yfEqp%2Funknown.png?alt=media\&token=7f9bccfe-0834-4e32-8495-ef9101a9f985)
9. Click **Connect** next to the OvalEdge Remote MCP Server.

   ![](https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2FLbJ2tzl0tiDseSRFNx0p%2Funknown.png?alt=media\&token=7fbc1f10-09ad-43ad-ae0a-560bd27f60c3)
10. When the browser prompts to open the Cursor application, optionally select **Always allow to open links of this type in the associated app**.

    ![](https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2Fjoa1NLW51cazD5MP8sMT%2Funknown.png?alt=media\&token=550e061c-ffbf-494b-abe6-901d5636a5e2)
11. Click **Open Cursor**.

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If already signed in to Cursor, the authentication process continues automatically and returns to the Cursor application.</p></div>
12. If not signed in to Cursor, the browser redirects to the **Okta** sign-in page. Enter the Okta username. Click **Next**. Complete the remaining authentication steps, including entering your password and completing any configured multi-factor authentication (MFA), if prompted.

    ![](https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2Fam8jRDSYNME5Vsiv8oX1%2Funknown.png?alt=media\&token=c1c3770d-9aec-4af4-a764-26e718c9ead3)
13. Wait until authentication completes successfully.
14. Return to the **Cursor** application.
15. Verify that the OvalEdge Remote MCP Server status changes to **Connected** and displays the available tools, prompts, and resources.

    ![](https://1227144352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgnJyYKHzsnoFOdZJtHsc%2Fuploads%2FqvqNPybG7KB89nPbTf3l%2Funknown.png?alt=media\&token=d1d7e7f8-ac7c-4b02-b9da-89cb08490aa2)
16. Open a new Cursor chat.
17. Select the configured OvalEdge Remote MCP Server.
18. Submit a sample metadata query to verify that the Remote MCP Server is responding successfully.
19. Review the returned response to confirm that the Cursor client can communicate with the OvalEdge Remote MCP Server using OAuth authentication.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/mcp-server/deployment-options/remote-mcp/remote-oauth-mcp/set-up-cursor-using-remote-oauth.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.