Connect UserVoice to Claude, ChatGPT, or Codex (MCP Setup and Authorization)

~ minute read

UserVoice MCP connects your own AI tool, such as Claude, ChatGPT, Codex, or GitHub Copilot Chat in VS Code, to your UserVoice data. Search ideas, summarize feedback, look up accounts, and make updates from the AI tool your team already uses.

Availability: Included in UserVoice's new plans. An account owner turns on MCP access in Settings → Integrations → AI Assistants. See Manage AI Assistant Access. Admins get access based on their permissions. Contributors get read-only access.

Prefer to work inside UserVoice? See UserVoice Agent vs. UserVoice MCP: Which Should I Use?

 

General Prerequisites 

You will need:

  • MCP access turned on for your UserVoice account. An account owner turns it on in Settings → Integrations → AI Assistants by selecting Enable Access to MCP (AI Agents). You only need to do this once per account.
  • A UserVoice admin or contributor login. The assistant acts on your behalf. Contributors have read-only access.
  • An AI assistant that supports remote MCP servers: Claude (claude.ai, desktop app, or Claude Code), ChatGPT, or Codex. Plan requirements for each are noted in the relevant section below.

Your MCP Server URL

It's the address you sign in to UserVoice on, followed by /api/v2/admin/mcp: https://<your-uservoice-domain>/api/v2/admin/mcp

If you sign in to UserVoice at… Your MCP server URL is…
acme.uservoice.com https://acme.uservoice.com/api/v2/admin/mcp
feedback.acme.com (a custom domain) https://feedback.acme.com/api/v2/admin/mcp

Using a custom domain? You must use your custom domain in the MCP URL. If you enter the uservoice.com address instead, saving works, but sign-in fails with an "issuer mismatch" error. To check which one you have, sign in to your UserVoice admin console and look at the address bar.

Write actions modify live data. The connector includes tools that create ideas, record a customer's feedback, add voters, flag ideas as important, update ideas (public and internal status, labels, owner, and details), link ideas to existing Jira issues or Azure DevOps work items, add ideas to lists or remove them, and merge, delete, or mark ideas as spam. A public status change posts a message on your portal and emails the idea's contributors, and it can't be undone. Contributors can't make changes.

Claude

Your setup path depends on your Claude subscription:

  • Team or Enterprise Plans (For Organization Owners): Follow Step 1A. Organization owners must configure this globally for the workspace, as individual team members cannot add custom connectors themselves.

  • Individual Plans (For Personal Use): Skip directly to Step 1B to set up the connector for your own account.

Step 1A: Make UserVoice Available to Your Team

(Note: If you use an individual Claude plan, skip to Step 1B).

As a Claude organization owner, you only need to add UserVoice once as an organization-level connector. Once added, it will automatically appear in every team member's Connectors list, and each member will then sign in using their own unique UserVoice credentials.

  1. In claude.ai, open your organization admin settings and go to Connectors.
  2. Choose Add custom connector. Make sure you are adding it at the organization level, not to your personal connector list.
  3. Fill in the form:
    • Name: UserVoice
    • Remote MCP server URL: https://<your-uservoice-domain>/api/v2/admin/mcp (see Your MCP server URL above; custom-domain accounts must use their custom domain)
  1. Save. If the form offers a toggle to make the connector available to members or to specific groups, enable it for everyone who should have access.
  1. Continue to Step 2 below to authorize the connection to your account.

 If you have more than one UserVoice subdomain, add a separate connector for each with a distinct name (for example "UserVoice Product" and "UserVoice Support"). Claude uses the connector name to decide which one to call, so you can say "search UserVoice Support for..." to target the right account.

 

Step 1B: Add UserVoice as a Personal Connector

On an individual Claude plan you add the connector to your own account instead. 

  1. In claude.ai, open your Settings and navigate to the Connectors tab.

  2. Choose Add custom connector.

  3. Fill in the connector details:

    • Name: UserVoice

    • Remote MCP server URL: https://<your-uservoice-domain>/api/v2/admin/mcp (Replace <your-uservoice-domain> with the address you sign in to UserVoice on, for example acme.uservoice.com or feedback.acme.com.)

  4. Click Save.

  5. Continue to Step 2 below to authorize the connection to your account.

Step 2: Connect and Authorize

Each person connects once and signs in with their own UserVoice account. The Claude desktop app shows the same Connectors list as claude.ai.

  1. In Claude, open Customize and then Connectors (or open the settings menu and choose Connectors). Under Your custom connectors you will see UserVoice with your subdomain listed beneath it.

  2. Click the UserVoice card, then click Connect. A new browser tab opens on your Uservoice sign-in page. If you're not already signed in, sign in the way you normally sign in to the Uservoice admin console, including with SSO if your site uses it.

  3. On the authorization page, confirm the application is Claude with the verified domain claude.ai, check that the Account and Signed in as fields show the UserVoice account you expect, and click Authorize.

  4. You are returned to Claude and the connector shows Connected. The connector page lists the UserVoice tools now available to Claude.

Note: If you are using the Claude desktop app and UserVoice does not appear in your Connectors list after your organization owner added it, quit and reopen the app.

Step 3: Use UserVoice in a Chat

  1. Start a new chat and click the + button in the message box, then hover over Connectors.
  2. Make sure the UserVoice toggle is on. Connectors you have authorized are usually on by default.
  3. Ask a question. Naming UserVoice in your prompt helps Claude pick the right connector, for example:
    • "What are the most-voted ideas in UserVoice from the last 30 days?"
    • "Summarize the feedback we have from Acme Corp in UserVoice."
    • "Group open UserVoice ideas by category and show counts."

The first time Claude uses a tool in a conversation it may ask you to approve the action. Write actions such as updating an idea's status will always be visible in the conversation.
Claude Code

If you use the Claude Code CLI, you can add the connector from your terminal. Connections added this way also appear in the Claude Code app.

claude mcp add --transport http UserVoice https://<your-uservoice-domain>/api/v2/admin/mcp

Replace <your-uservoice-domain> with the address you sign in to UserVoice on. If your account uses a custom domain, use it here, not your uservoice.com address.

 

The first time Claude Code uses the connection, it opens your browser to the UserVoice authorization page. Sign in and click Authorize. To remove the connection later, run:

claude mcp remove UserVoice

To connect more than one subdomain, run the add command once per subdomain with a different name in place of "UserVoice".

ChatGPT

ChatGPT supports remote MCP servers through its Apps settings in developer mode. Two things to know before you start:

  • Plan requirements. Full read and write access requires a ChatGPT Business, Enterprise, or Edu workspace. On ChatGPT Pro, custom MCP servers are limited to read-only tools, so you can query UserVoice but not update ideas. Free and Plus plans do not support custom MCP servers.
  • Workspace admin step. On Business, Enterprise, and Edu plans, a workspace owner or admin must turn on developer mode and publish the connector before members can use it. Individual members cannot add it on their own.

Step 1: Create and Publish the UserVoice App

  1. Verify your workspace permissions. Only workspace owners or administrators have the ability to enable developer mode and publish custom apps. If you don't have these permissions, you won't be able to see the settings in the following steps.

  2. Enable developer mode. On Business plans, go to Workspace settings, then Apps, then Advanced settings, and turn on Developer mode. On Enterprise and Edu plans, first grant developer access under Permissions & Roles, then Connected Data.
  3. Go to Apps and choose Create.
  4. Fill in the form:
    • Name: UserVoice

    • MCP server URL: https://<your-uservoice-domain>/api/v2/admin/mcpAuthentication: choose OAuth. Do not enter a client ID or client secret; ChatGPT registers itself with UserVoice automatically.

      Replace <your-uservoice-domain> with the address you sign in to UserVoice on. If your account uses a custom domain, use it here.

  5. Click Scan Tools. A UserVoice sign-in window opens. Sign in with your UserVoice admin credentials, confirm the authorization page shows ChatGPT as the application, and click Authorize. Wait for the tool scan to finish and confirm the UserVoice tools are listed.

  6. Click Create.
  7. Publish it to your workspace: go to Workspace settings, then Apps, then Drafts, and click Publish.
    • On Enterprise and Edu plans you can use Configure Actions first to restrict which UserVoice tools members may use, for example to allow read tools only.

 

Step 2: Connect Your UserVoice Account in ChatGPT

  1. Make sure developer mode is enabled for your account: Settings, then Apps, then Advanced settings.
  2. Open Settings, then Apps, find UserVoice and click Connect.
  3. Sign in to UserVoice when prompted and click Authorize. Each person authorizes with their own UserVoice login.
  4. In a chat, click the + button, open Developer mode (or the Apps/tools list), and turn on UserVoice. Then ask a question, for example "What are the top-voted ideas in UserVoice this month?"

Note: ChatGPT asks you to confirm before running write actions such as updating an idea. Read actions run without confirmation.
Codex

Codex (OpenAI’s coding agent) can connect from the terminal or from the Codex app and IDE extension. Both use the same UserVoice sign-in and authorization page.

Codex CLI

  1. Add the server:
codex mcp add UserVoice --url https://<your-uservoice-domain>/api/v2/admin/mcp

Replace <your-uservoice-domain> with the address you sign in to UserVoice on. If your account uses a custom domain, use it here.

  1. Sign in. Codex detects that UserVoice uses OAuth and may open your browser immediately; if it does not, run:
codex mcp login UserVoice
  1. In the browser tab that opens, sign in to UserVoice and click Authorize. Return to the terminal; Codex reports the login as complete.
  2. Verify with codex mcp list and start using it: codex then ask, for example, "Search UserVoice for ideas about SSO."

To remove the connection later, run:

codex mcp remove UserVoice

Codex App or IDE Extension

  1. Open Settings and choose MCP servers.
  2. Select Add server. Enter UserVoice as the name, choose Streamable HTTP as the type, and paste your MCP URL.
  3. Save, then select Restart when prompted.
  4. When Codex prompts you to authenticate, select Authenticate, sign in to UserVoice in the browser tab that opens, and click Authorize.

If you prefer editing config directly, the CLI stores the server in ~/.codex/config.toml as a [mcp_servers.UserVoice] entry with url = "https://<your-uservoice-domain>/api/v2/admin/mcp". Do not add a bearer token or client ID; the OAuth flow handles authentication.

Reference Guide

Available Tools & Capabilities

The connector exposes a set of tools that the assistant chooses from based on your request. At the time of writing these include:

  • Read: get_workspace_context, query_ideas, get_idea_details, aggregate_ideas, query_accounts, get_account_details, query_users, get_user_details, query_labels, query_idea_lists
  • Write: create_idea, create_feedback, add_idea_voters, flag_idea_important, unflag_idea_important, update_idea, update_idea_status, update_idea_public_status, update_idea_labels, assign_idea_owner, link_idea_to_issue, create_view, update_idea_list, merge_ideas, delete_idea, mark_idea_spam

You can see the current list on the connector's page in Claude, in the tool scan results in ChatGPT, or by running codex mcp get UserVoice in Codex.

Troubleshooting

 

  • Sign-in fails with "Issuer mismatch," or the connector won't stay connected after you click Authorize. Your UserVoice account uses a custom domain, and the connector was added with your uservoice.com address. Remove the connector and add it again using your custom domain:

    Claude (web/desktop): delete the UserVoice connector, then add it again with https://<your-custom-domain>/api/v2/admin/mcp. On Team and Enterprise plans, an organization owner has to do this.

    Claude Code:

    claude mcp remove UserVoice
claude mcp add --transport http UserVoice https://<your-custom-domain>/api/v2/admin/mcp

    Codex: 
    codex mcp remove UserVoicecodex mcp add UserVoice --url https://<your-custom-domain>/api/v2/admin/mcp

 

  • UserVoice is not in my Connectors list. Your Claude organization owner needs to add it first (Step 1). If they already have, quit and reopen the Claude desktop app or refresh claude.ai.
  • I see "Re-authorize" or a warning icon next to UserVoice. Your authorization has expired or been revoked. Click Re-authorize and sign in to UserVoice again.
  • The connection fails immediately after saving. Check that the OAuth Client ID and Client Secret fields were left blank, and that the URL ends in /api/v2/admin/mcp and uses the domain you sign in to UserVoice on (your custom domain, if you have one).
  • I do not see the authorization screen, or UserVoice returns an error. MCP access may be turned off for your UserVoice account, or the account you signed in with may not have admin or contributor access. Ask your UserVoice account owner to open Settings → Integrations → AI Assistants and check that Enable Access to MCP (AI Agents) is selected. If it is and you still see an error, contact UserVoice support.
  • Claude is using the wrong UserVoice account. If you have multiple connectors, mention the connector name in your prompt (for example "in UserVoice Support").
  • ChatGPT says custom apps are unavailable. Developer mode is off or your plan does not support it. On Business, Enterprise, and Edu plans an admin must enable it; on Pro only read tools are available; Free and Plus do not support custom MCP servers.

Which AI Assistants Can Connect

UserVoice uses OAuth 2.1 with PKCE for sign-in, and recognizes assistants through Client ID Metadata Documents (CIMD). This is the client registration method the current MCP specification recommends. With CIMD, an assistant identifies itself with a URL it publishes (for example, https://vscode.dev/oauth/client-metadata.json). UserVoice checks that document when you sign in, so you never enter a client ID or client secret. The consent page shows the assistant's verified domain so you can confirm who you're authorizing.

UserVoice does not support Dynamic Client Registration (DCR). That's the older method, where an assistant registers itself with the server on first connect. The MCP specification deprecated DCR in its 2026-07-28 revision in favor of CIMD.

Works today: Claude (claude.ai, desktop app, and Claude Code), ChatGPT, Codex, and GitHub Copilot Chat in Visual Studio Code.

Not supported yet:

  • Cursor: it supports only DCR for now. Cursor has said CIMD support is planned, with no date yet.
  • GitHub Copilot CLI: its OAuth support uses DCR.
  • GitHub Copilot cloud agent and Copilot code review (github.com): these don't currently support remote MCP servers that use OAuth.

If an assistant asks for a client ID or secret, leave both blank. If it fails with a client-registration error, it probably supports only DCR.

Security and Permissions

Authorization uses OAuth: the assistant never sees your UserVoice password, and you can revoke access at any time by disconnecting the connector in Claude, ChatGPT, or Codex. An account owner can also turn off MCP access for the whole account in Settings → Integrations → AI Assistants. Every connected assistant loses access right away.

 The assistant acts with the same permissions as the UserVoice account you signed in with, so it can only see and change what you can. Each team member authorizes individually; an administrator adding the connector to a workspace does not grant anyone access to your account.

 

Related to

Related articles