Connect Cursor to your team’s docs

Note: Cursor’s settings screens change between versions. The mcp.json file below is the stable way to add a server; the MCP section of Cursor’s settings shows the same list.

1. 1

   Step 1: Choose where the server lives

   Use ~/.cursor/mcp.json to have the repository in every project, or .cursor/mcp.json inside one project to keep it there. A project file can be committed so the whole team gets the server.

2. 2

   Step 2: Add the endpoint

   Add the repository under mcpServers with its endpoint as the url. Cursor supports OAuth for remote servers: when it reports that the server needs a login, start it from the MCP settings, sign in to Notedigit in the browser and choose Authorize.

   {
     "mcpServers": {
       "project-knowledge": {
         "url": "https://notes.your-company.com/mcp/<repository-id>"
       }
     }
   }

3. 3

   Step 3: Or use an access token

   If you prefer not to sign in through the browser, create a personal access token in Notedigit (Settings → Access tokens) and send it as a header. Keep the token in an environment variable rather than in the file: Cursor reads ${env:NAME} in url and headers.

   Tokens act as you, last 90 days, and can be revoked at any time.

   {
     "mcpServers": {
       "project-knowledge": {
         "url": "https://notes.your-company.com/mcp/<repository-id>",
         "headers": {
           "Authorization": "Bearer ${env:NOTEDIGIT_TOKEN}"
         }
       }
     }
   }

4. 4

   Step 4: Use it in the agent

   Once the server shows as connected, Cursor’s agent can call search, read_file and list_files on the repository. It cannot change anything there.

   Every call appears in Notedigit under MCP connections, with Cursor as the client.