Connect Notiondesk Workspace MCP to Claude Code to review workspace information and perform supported Notiondesk actions directly from your terminal.
Claude Code connects to Notiondesk as a remote HTTP MCP server and authenticates through OAuth.
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
- Claude Code is installed and working on your computer
If Workspace MCP is not enabled yet, see Enable Workspace MCP in Notiondesk.
Add Notiondesk MCP to Claude Code
Run:
claude mcp add --transport http notiondesk https://mcp.notiondesk.so/mcpThis adds the Notiondesk Workspace MCP server to Claude Code.
Make Notiondesk available across all projects
If you want to use Notiondesk MCP from every Claude Code project, add it with user scope:
claude mcp add --transport http --scope user notiondesk https://mcp.notiondesk.so/mcpUse project or local scope instead if you only want the connection available in a specific development environment.
Authenticate with Notiondesk
After adding the server, start Claude Code:
claudeThen enter:
/mcpSelect the notiondesk server and start the authentication flow.
Claude Code opens Notiondesk in your browser.
Then:
- Sign in to Notiondesk if needed.
- Confirm that the correct workspace is displayed.
- Review the requested permissions.
- Approve the connection.
- Return to Claude Code.
Claude Code stores the OAuth authentication for the connection and can refresh it when necessary.
Verify the MCP server
You can check configured MCP servers from your terminal:
claude mcp listYou can also inspect the Notiondesk server:
claude mcp get notiondeskThen start Claude Code and test the connection with:
List the Notiondesk help centers I can access.Confirm that the expected help centers appear.
Next, try:
Show the sync status for my main help center.Starting with read-only requests helps confirm that Claude Code is connected to the correct Notiondesk workspace.
Use Notiondesk from Claude Code
Once connected, Claude Code can use available Notiondesk tools when they are relevant to your request.
For example:
Review recent article feedback and search analytics. Show me which documentation needs attention first.Or:
Review recent chatbot conversations and identify repeated questions that are not covered well by our help center.If your Notiondesk role allows changes, you can also ask Claude Code to perform supported actions:
Trigger a sync for the onboarding collection.The actions available to Claude Code depend on your Notiondesk workspace permissions.
Work with multiple help centers
The same Claude Code 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 configure a separate MCP server for each help center.
When several help centers are available, specify the one you want Claude Code to use.
For example:
Check the French translation status for the Developer Docs help center.Choose the right Claude Code scope
Claude Code supports different scopes for MCP servers.
Local scope
Local scope is the default.
Use it when you only need Notiondesk MCP in the current project.
claude mcp add --transport http notiondesk https://mcp.notiondesk.so/mcpProject scope
Use project scope when the MCP configuration should be shared with teammates through the project's .mcp.json configuration.
claude mcp add --transport http --scope project notiondesk https://mcp.notiondesk.so/mcpEach teammate still authenticates with their own Notiondesk account.
Do not share OAuth credentials between teammates.
User scope
Use user scope when you want Notiondesk available across all Claude Code projects on your computer:
claude mcp add --transport http --scope user notiondesk https://mcp.notiondesk.so/mcpFor most people who regularly manage Notiondesk from Claude Code, user scope is the most convenient option.
Permissions
Workspace MCP follows the permissions of the Notiondesk teammate who completes OAuth authorization.
For example:
- A Viewer can use supported read-only tools
- An Editor can access supported management actions
- An Admin or workspace owner can access additional administrative actions
Adding Notiondesk MCP to a shared project does not share one teammate's Notiondesk permissions with everyone else.
Each teammate authenticates separately.
Troubleshooting
Claude Code cannot find the Notiondesk MCP server
Run:
claude mcp listConfirm that notiondesk appears.
If it does not, add it again:
claude mcp add --transport http notiondesk https://mcp.notiondesk.so/mcpOAuth authentication does not start
Open Claude Code and enter:
/mcpSelect the Notiondesk server and start authentication.
If your browser does not open automatically, Claude Code may provide a URL that you can open manually.
The Notiondesk server is added but not authenticated
Use:
/mcpThen select the Notiondesk server and complete the OAuth flow.
Adding the MCP server and authenticating your Notiondesk account are separate steps.
A help center is missing
Confirm that:
- Workspace MCP is enabled for that help center
- Your Notiondesk account has access to it
Claude Code cannot access a help center that is unavailable to the account used during OAuth authorization.
Some actions are unavailable
Workspace MCP follows your Notiondesk role.
If Claude Code can read information but cannot perform a particular action, your account may not have the required permission.
See Workspace MCP roles, permissions, and security for details.
Authentication stops working
Open:
/mcpSelect the Notiondesk server and authenticate again.
You can also clear the existing authentication from the MCP menu before reconnecting.
Remove Notiondesk MCP
To remove the server from Claude Code:
claude mcp remove notiondeskRemoving the server from Claude Code does not disable Workspace MCP in Notiondesk and does not affect connections from other AI clients.