Connect the MCP server to ChatGPT

Goveda Pro exposes its examination workflow as an MCP server, so you can drive it conversationally from ChatGPT — create and open projects, upload an application, run prior art search, and review results, all in chat.

Before you start — you'll need a Goveda Pro account (the same one you use for the web app; your organization and projects are shared across both) and a ChatGPT plan that supports Developer Mode (Plus, Pro, or Business, on the web). The server URL is https://gp-mcp.goveda.com/mcp.

Connect to ChatGPT

Goveda Pro connects as a custom app in ChatGPT's Developer Mode and authenticates by signing in to your Goveda Pro account in the browser (OAuth).

Signing in is the only way to connect. API keys are not supported for MCP connections — don't add an apikey parameter to the server URL, and don't choose No Auth.

Enable Developer Mode

In ChatGPT, go to Settings → Apps → Advanced and toggle on Developer Mode. This lets you add custom MCP apps.

ChatGPT's Apps settings with Developer Mode toggled on

Create an app

Back on the Apps page, click Create app. The New App dialog opens.

Enter the Goveda Pro details

Fill in the dialog:

  • Name — Goveda Pro
  • Connection — Server URL
  • URL — https://gp-mcp.goveda.com/mcp
  • Authentication — OAuth
ChatGPT's New App dialog with the server URL and OAuth selected

Acknowledge and create

Check the acknowledgment box, then click Create. A window opens to complete sign-in.

Authorize

Authenticate with your Goveda Pro account and click Connect to approve access. Goveda Pro is then added to ChatGPT with its tools available.

The Goveda Pro authorization window in ChatGPT with a Connect button

Signing in with your organization's SSO

If your organization signs in through its own identity provider — Microsoft Entra ID, Okta, or similar — authorizing the app works exactly like signing in to the web app. There is no separate SSO option to choose.

  • Enter your work email. The sign-in window asks for your email first. If your organization's domain is set up for single sign-on, you're sent to your identity provider to authenticate. You're never asked for an organization name.
  • The organization comes from the sign-in. If you belong to more than one Goveda Pro organization, you're asked which one to use, and the app stays bound to it — every tool then acts in that organization. To work in a different one, reconnect and pick it during sign-in.
  • Where SSO is enforced, it's the only way in. Password and social sign-ins no longer satisfy the policy, and API keys are not an alternative route — the app has to be authorized through your identity provider.
  • If sign-in is refused, ask your organization's Owner to check your access. They manage single sign-on under Settings → Organization → Security & SSO, including linking existing members to the identity provider.

What you can do

Once connected, you can run the examination workflow from chat:

  • Create and open projects
  • Upload an application and read it — bibliographic data, full text, and the AI summary
  • Search and read the reference PDFs in a Project's Knowledge Base
  • Run prior art search and inspect the results, plus the system's recommended prior art
  • Review the Lack of Unity analysis and export prior art to CSV

For the full workflow, see How it works. For the exact tools available — and what's still on the roadmap — see the Tool reference. For end-to-end examples, see Sample sessions.