Connect Notiondesk Workspace MCP to another MCP client

You can connect Notiondesk Workspace MCP to any compatible AI client that supports remote MCP servers and OAuth authentication.

Use this guide when your MCP client does not have a dedicated Notiondesk installation guide.

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

• Your MCP client supports remote HTTP MCP servers

• Your MCP client supports OAuth authentication

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

Connection details

Use these details when adding Notiondesk to your MCP client:

Name: Notiondesk MCP
URL: https://mcp.notiondesk.so/mcp
Authentication: OAuth

Do not add /sse to the URL.

The Workspace MCP endpoint is:

https://mcp.notiondesk.so/mcp

Add the MCP server

Open your AI client's MCP or connector settings.

The exact interface depends on the client, but you will typically need to:

1. Add a new remote MCP server

2. Enter Notiondesk MCP as the name

3. Enter https://mcp.notiondesk.so/mcp as the server URL

4. Select OAuth authentication if your client asks for an authentication method

5. Save or connect the server

If your MCP client uses a configuration file instead of a settings interface, add Notiondesk as a remote HTTP MCP server using the same URL.

Consult your client's MCP documentation for its exact configuration format.

Authenticate with Notiondesk

After adding the server, start the connection or authentication flow.

Your client should open Notiondesk in your browser.

Then:

1. Sign in to Notiondesk if needed

2. Confirm that the correct workspace is displayed

3. Review the requested permissions

4. Approve the connection

5. Return to your MCP client

Workspace MCP uses OAuth, so you should not need to manually copy a Notiondesk password or API key into your MCP client.

Verify the connection

Start with a read-only request:

List the Notiondesk help centers I can access.

Confirm that the expected help centers appear.

Then try:

Show the sync status for my main help center.

You can also ask:

Show me the latest negative article feedback.

Starting with read-only requests helps confirm that the client is connected to the correct Notiondesk workspace before performing actions.

Use Workspace MCP

Once connected, your MCP client can use the Notiondesk tools available to your account.

For example:

Review our article feedback and analytics from the last 30 days. Show me which articles need attention first.

Or:

Check the translation status for my main help center.

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

Trigger a sync for the onboarding collection.

The exact way your client discovers or invokes MCP tools depends on the client.

Permissions

Workspace MCP follows the permissions of the Notiondesk teammate who completes OAuth authorization.

Connecting through another MCP client does not change your Notiondesk permissions.

For example:

• A Viewer receives supported read-only access.

• An Editor can perform supported management actions.

• An Admin or workspace owner can access additional administrative actions.

The MCP client cannot gain more access than your Notiondesk account already has.

Work with multiple help centers

One Workspace MCP connection can provide access to multiple 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 a different Workspace MCP URL for each help center

The same endpoint is used:

https://mcp.notiondesk.so/mcp

When multiple help centers are available, specify the one you want your assistant to use.

For example:

Review article feedback for the Developer Docs help center.

Troubleshooting

https://mcp.notiondesk.so/mcp

https://mcp.notiondesk.so/mcp/sse