Connect Notiondesk Workspace MCP to Codex

Connect Notiondesk Workspace MCP to Codex, authenticate with OAuth, and access Notiondesk tools from the Codex CLI or IDE extension.

4 min read

Connect Notiondesk Workspace MCP to Codex to review workspace information and perform supported Notiondesk actions from the Codex CLI or IDE extension.

Notiondesk runs as a remote MCP server and uses OAuth to authenticate your Notiondesk account.

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
  • Codex is installed and working on your computer

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

Add Notiondesk MCP to Codex

Run:

codex mcp add notiondesk --url https://mcp.notiondesk.so/mcp

This adds the Notiondesk Workspace MCP server to your Codex configuration.

Authenticate with Notiondesk

After adding the server, run:

codex mcp login notiondesk

Your browser opens the Notiondesk OAuth authorization page.

Then:

  1. Sign in to Notiondesk if needed.
  1. Confirm that the correct workspace is displayed.
  1. Review the requested permissions.
  1. Approve the connection.
  1. Return to Codex.

You do not need to add a Notiondesk API key, password, or token manually.

Authentication is handled through OAuth.

Verify the connection

Check your configured MCP servers:

codex mcp list

Confirm that notiondesk appears and is enabled.

You can then start Codex:

codex

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.

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

Use Workspace MCP from Codex

Once connected, Codex can use available Notiondesk tools when they are relevant to your task.

For example:

Review the last 30 days of article feedback and analytics. Show me which documentation needs attention first.

Or:

Review recent chatbot conversations and identify repeated customer questions that are not covered well by our documentation.

If your Notiondesk role allows supported changes, you can also ask Codex to perform actions:

Trigger a sync for the onboarding collection.

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

Use Notiondesk MCP from the Codex IDE extension

Codex shares its MCP configuration between the CLI and supported IDE integrations.

After configuring Notiondesk with:

codex mcp add notiondesk --url https://mcp.notiondesk.so/mcp

the same MCP server can be available from the Codex IDE extension.

If the extension was already open when you added the server, reload it if Notiondesk does not appear.

Each authenticated Notiondesk connection continues to follow your own workspace permissions.

Configure Notiondesk manually

Codex stores its MCP configuration in:

~/.codex/config.toml

You can configure Notiondesk manually with:

[mcp_servers.notiondesk]
url = "https://mcp.notiondesk.so/mcp"

After saving the configuration, authenticate with:

codex mcp login notiondesk

Using codex mcp add is usually simpler than editing the configuration manually.

Work with multiple help centers

One Codex 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 which one Codex should work with:

Check the French translation status for the Developer Docs help center.

Permissions

Workspace MCP follows the permissions of the Notiondesk account used during OAuth authorization.

For example:

  • Viewers can access supported read-only information
  • Editors can perform supported management actions
  • Admins and workspace owners can access additional administrative actions

Connecting Notiondesk to Codex does not give your account additional Notiondesk permissions.

Troubleshooting

Notiondesk does not appear in Codex

Run:

codex mcp list

Confirm that notiondesk appears.

If it does not, add the server again:

codex mcp add notiondesk --url https://mcp.notiondesk.so/mcp

Notiondesk is configured but not authenticated

Run:

codex mcp login notiondesk

Adding the MCP server and completing OAuth authentication are separate steps.

OAuth authentication does not open

Confirm that the Workspace MCP URL is:

https://mcp.notiondesk.so/mcp

Then retry:

codex mcp login notiondesk

Do not add /sse to the Workspace MCP URL.

A help center is missing

Confirm that:

  • Workspace MCP is enabled for that help center.
  • Your Notiondesk account has access to it.

Codex 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.

If Codex can read workspace information but cannot perform an action, your account may not have the required permission.

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

The server appears in codex mcp list but is not available in a session

Start a new Codex session after configuring the MCP server.

If you use the IDE extension, reload it after changing your MCP configuration.

Remove Notiondesk MCP

To remove the connection from Codex, use the MCP management commands available in your installed Codex version.

You can also remove the notiondesk entry from:

~/.codex/config.toml

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

Related articles

Was this page helpful?