Connect Notiondesk Workspace MCP to VS Code

Connect Notiondesk Workspace MCP to Visual Studio Code to access your Notiondesk workspace from VS Code's AI tools.

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

• You are using a version of VS Code with MCP support

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

Connect Notiondesk from the dashboard

The easiest setup starts from Notiondesk.

1. Open your Notiondesk dashboard

2. Select a help center where Workspace MCP is enabled.

3. Go to Settings → General

4. Find the Workspace MCP section

5. Open Install in your client

6. Select VS Code

7. Click Add to VS Code

VS Code opens the Notiondesk MCP server details.

1. Review the server name and URL

2. Click Install

3. Start the server if VS Code asks you to

4. Complete the Notiondesk OAuth authorization in your browser

Once authorization is complete, Notiondesk tools become available in VS Code.

Configure Notiondesk MCP manually

You can also configure Workspace MCP with VS Code's mcp.json file.

For a project-specific connection, create or open:

.vscode/mcp.json

Add:

{
  "servers": {
    "notiondesk": {
      "type": "http",
      "url": "https://mcp.notiondesk.so/mcp"
    }
  }
}

Save the file.

VS Code should detect the new MCP server.

Make Notiondesk available across all projects

If you use Notiondesk regularly across different projects, you can add the server to your VS Code user profile instead of a single workspace.

Open the Command Palette and run:

MCP: Add Server

Add the remote HTTP server:

https://mcp.notiondesk.so/mcp

Choose your user profile as the configuration target.

A user-level MCP server is available across your VS Code workspaces.

Start the Notiondesk MCP server

Open the Command Palette and run:

MCP: List Servers

Select notiondesk.

From there, you can start, stop, restart, or inspect the server.

When starting the connection for the first time, VS Code may ask you to confirm that you trust the MCP server.

Review the configuration and approve it to continue.

Authenticate with Notiondesk

When VS Code connects to Notiondesk Workspace MCP, it starts the OAuth authorization flow.

Notiondesk opens 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 VS Code

Verify the connection

Start with a read-only request in VS Code:

List the Notiondesk help centers I can access.

Confirm that the expected help centers are returned.

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 customer questions.

Start with read-only requests before asking VS Code to perform changes.

Use Workspace MCP from VS Code

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

For example:

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

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

Trigger a sync for the onboarding collection.

Available tools depend on your Notiondesk role and the help centers you can access.

Work with multiple help centers

The same VS Code connection can access multiple Notiondesk help centers.

A help center is available when:

• Workspace MCP is enabled for it

• Your Notiondesk account has permission to access it

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

When working with several help centers, specify which one you mean:

Check the translation status for the Developer Docs help center.

Workspace vs user configuration

Use a workspace configuration when Notiondesk MCP should only be configured for one project:

.vscode/mcp.json

Use a user configuration when you want Notiondesk MCP available in all your VS Code workspaces.

If a workspace configuration is committed to source control, other teammates can receive the same MCP server definition, but each teammate must still authenticate with their own Notiondesk account.

Do not share OAuth credentials between teammates.

Troubleshooting

MCP: List Servers

{
  "servers": {
    "notiondesk": {
      "type": "http",
      "url": "https://mcp.notiondesk.so/mcp"
    }
  }
}

MCP: List Servers

https://mcp.notiondesk.so/mcp

Disconnect Notiondesk from VS Code

You can disable or remove the Notiondesk MCP server from VS Code when you no longer want it available.

Run:

MCP: List Servers

Select the Notiondesk server and disable or remove it.

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

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