Connect Notiondesk Workspace MCP to Cursor

Connect Notiondesk Workspace MCP to Cursor to access your Notiondesk workspace while working with Cursor's AI agent.

You can install the connection directly from Notiondesk or configure the remote MCP server manually.

Workspace MCP uses OAuth and follows the permissions of the Notiondesk teammate who authorizes the connection.

Before you start

Make sure:

Workspace MCP is enabled for at least one Notiondesk help center

You can sign in to the Notiondesk workspace you want to connect

Cursor is installed and signed in

If Workspace MCP is not enabled yet, see Enable Workspace MCP in Notiondesk.

Connect Notiondesk to Cursor

The easiest method is the one-click installation from Notiondesk.

Open your Notiondesk dashboard

Select a help center where Workspace MCP is enabled

Go to Settings → General

Find the Workspace MCP section

Open Install in your client

Select Cursor

Click Add to Cursor

Approve the installation in Cursor

Once authorization is complete, Notiondesk MCP becomes available to Cursor.

Configure Notiondesk MCP manually

You can also add Workspace MCP directly to Cursor's MCP configuration.

For a connection available across all your projects, open or create:

~/.cursor/mcp.json

Add:

{
  "mcpServers": {
    "notiondesk": {
      "url": "https://mcp.notiondesk.so/mcp"
    }
  }
}

Save the file.

Cursor also supports project-specific MCP configuration in:

.cursor/mcp.json

Use the global configuration if you want Notiondesk available across all Cursor projects.

Authenticate with Notiondesk

After adding the server, open Cursor's MCP settings and find the Notiondesk connection.

Start the authentication flow when prompted.

Notiondesk opens in your browser.

Before approving access:

Confirm that the correct Notiondesk workspace is displayed.

Review the requested permissions.

Approve the connection.

Return to Cursor.

The connection uses OAuth. You do not need to put a Notiondesk API key or password in mcp.json.

Verify the connection

Start with a read-only request in Cursor:

List the Notiondesk help centers I can access.

Confirm that Cursor returns the expected help centers.

Then try:

Show the sync status for my main help center.

You can also ask:

Show me the latest negative article feedback.

Or:

Review recent chatbot conversations and identify repeated questions.

Starting with read-only requests makes it easier to confirm that Cursor is connected to the correct workspace before performing actions.

Use Workspace MCP from Cursor

Once connected, Cursor can use available Notiondesk MCP tools when they are relevant to your request.

For example:

Review our recent article feedback and search analytics. Show me the documentation gaps we should address first.

If your Notiondesk role allows changes, you can also request supported actions:

Trigger a sync for the onboarding collection.

The tools and actions available to Cursor depend on your Notiondesk permissions.

Work with multiple help centers

The same Cursor MCP connection can access multiple Notiondesk help centers.

A help center is available when:

Workspace MCP is enabled for it.

Your Notiondesk account has access to it.

You do not need to create a separate MCP server configuration for every help center.

When several help centers are available, specify which one Cursor should use:

Check the translation status for the Developer Docs help center.

Troubleshooting

Notiondesk does not appear in Cursor

Check that the MCP server has been added successfully.

If you configured it manually, confirm that your mcp.json contains:

{
  "mcpServers": {
    "notiondesk": {
      "url": "https://mcp.notiondesk.so/mcp"
    }
  }
}

Then reload Cursor if necessary.

OAuth authentication does not start

Confirm that the Workspace MCP URL is exactly:

https://mcp.notiondesk.so/mcp

Do not add /sse or modify the URL.

Then open Cursor's MCP settings and retry the authentication flow.

A help center is missing

Confirm that:

Workspace MCP is enabled for that help center

Your Notiondesk account has access to it

Cursor cannot access a help center that is unavailable to the Notiondesk account used during OAuth authorization.

Some Notiondesk tools are unavailable

Workspace MCP follows your Notiondesk role.

For example, a teammate with read-only access will not receive the same actions as an Admin.

See Workspace MCP roles, permissions, and security for details.

Cursor can read data but cannot perform an action

Your Notiondesk role may not allow that action.

Some actions may also require confirmation before Workspace MCP performs them.

Disconnect Notiondesk from Cursor

You can remove or disable the Notiondesk MCP server from Cursor when you no longer want Cursor to access it.

If you configured it manually, remove the notiondesk entry from your mcp.json.

Removing the connection from Cursor does not disable Workspace MCP in Notiondesk and does not affect other teammates or AI clients.

Table of contents