One server URL works in every client. Choose your client below for its exact steps, or follow the three steps that work in any client that supports remote MCP.
Choose your connection
One URL, two ways to sign in
https://govcondash.ai/api/mcp
Sign in (recommended)
Most clients sign in through OAuth: the client finds the GovConDash sign-in on its own, you sign in to your GovConDash account and choose Allow. Nothing to copy, and you can disconnect it at any time.
Agent key
For a client that takes a fixed header, mint an agent key on the Connected agents tab of your Account page and send it as Authorization: Bearer followed by the key. The key is shown once; revoke it there when you no longer need it.
Connect GovConDash to any MCP client
1Add a new MCP server or custom connector in your client.
2Paste the GovConDash MCP URL and name it GovConDash.
3Sign in to GovConDash and choose Allow.
Included with Pro and Max. Every tool reads under your own account. See plans
ChatGPT
Sign in (OAuth)
Add GovConDash as a custom connector and use it in chat and deep research.
1In ChatGPT on the web, go to Plugins, select the plus button, then select Add custom MCP server.
2Name it GovConDash and, under Connection, paste the server URL.
3Set authentication to OAuth, select the I understand and want to continue checkbox, and select Create as a plugin.
4Sign in to your GovConDash Pro or Max account when prompted and choose Allow.
5Install the plugin, start a new conversation, type @, select GovConDash, and ask a question.
Custom MCP servers are available on ChatGPT Business and Enterprise/Edu, on the web only. On Business only admins and owners can add them; on Enterprise/Edu an admin can grant members permission. Only admins and owners can publish them for the workspace.
Sign in (OAuth) or Agent key (Authorization header)
Add GovConDash as a custom connector in claude.ai and Claude Desktop.
1In claude.ai or Claude Desktop, open Customize, then Connectors, then Add custom connector.
2Name it GovConDash and paste the server URL. Under OAuth client, choose Register automatically.
3Choose Add, then Connect, sign in to your GovConDash Pro or Max account, and choose Allow.
4In a chat, choose the + button, select Connectors, turn GovConDash on, and ask a question.
Agent key (Authorization header)
text
Authorization: Bearer gcd_mcp_YOUR_AGENT_KEY
On a Team or Enterprise plan an Owner adds the connector once under Organization settings, then Connectors, then Add, Custom, Web, and each member connects their own account. The Free plan can add one custom connector. To use an agent key instead (request headers are a beta offered to a limited set of organizations), choose No sign-in and add the Authorization header below under Request headers, with Bearer before the key; an OAuth connection cannot also carry an Authorization header.
Sign in (OAuth) or Agent key (Authorization header)
Add GovConDash to Claude Code with one command, signing in through the browser or with an agent key.
1Run the add command below in your terminal (add --scope user to make it available in every project).
2Start Claude Code, run /mcp, and follow the steps in your browser to log in to your GovConDash Pro or Max account, then choose Allow. Skip this step if you used the agent key command.
3Back in Claude Code, ask a question; the GovConDash tools appear in /mcp.
Sign in (OAuth)
bash
claude mcp add --transport http govcondash https://govcondash.ai/api/mcp
Sign in (OAuth) or Agent key (Authorization header)
Add GovConDash to the Codex CLI and IDE extension through config.toml.
1Add the govcondash entry below to ~/.codex/config.toml.
2For the sign-in path, run codex mcp login govcondash and sign in to your GovConDash Pro or Max account. For the key path, export GOVCONDASH_MCP_KEY with your agent key before starting Codex.
3Start Codex, run /mcp to confirm the GovConDash tools are listed, and ask a question.
This guide covers the Gemini CLI. Custom MCP servers in the Gemini app depend on the account's plan and region; follow Google's documentation for your account.
Add GovConDash to a Microsoft 365 Copilot declarative agent as an MCP plugin.
1In Visual Studio Code, open the Microsoft 365 Agents Toolkit, select Create a New Agent/App, then Declarative Agent.
2Select Add an Action, then Start with an MCP Server, and enter the server URL.
3For the authentication type choose OAuth (with dynamic registration): GovConDash registers the client at runtime, so no client ID or secret is needed. Then choose a project location and name the agent.
4In the Accounts pane sign in to Microsoft 365, then in the Lifecycle pane select Provision and Confirm.
5Open https://m365.cloud.microsoft/chat, pick your agent under Agents, ask a question, and choose Sign in when prompted to sign in to your GovConDash Pro or Max account and choose Allow.
Needs a Microsoft 365 Copilot license, and your Microsoft 365 account must show Custom App Upload Enabled and Copilot Access Enabled in the toolkit (ask your admin otherwise). To build the agent without code in the browser, use the Microsoft Copilot Studio guide instead.
Add GovConDash as a remote connector in Perplexity.
1In Perplexity, open Plugins in the sidebar (or Customize, then Connectors), then Add custom, then Connector, then Add MCP connector, and select Remote.
2Enter the name GovConDash and the MCP Server URL, set Authentication to OAuth 2.0 and Transport to Streamable HTTP.
3Check the acknowledgement box, choose Add, then choose the connector card to sign in to your GovConDash Pro or Max account and enable it.
4Ask a question in a new thread.
In an organization, admins must turn on Allow members to add custom connectors (off by default), or add the connector under Enterprise settings. Remote connectors depend on your Perplexity plan.
For Grok Business and Enterprise, a team admin provisions the connector first. xAI's page does not say which sign-in methods a custom connector supports; if the grok.com sign-in fails, use the Grok CLI with an agent key. The xAI API takes the server too: pass server_url and an agent key as authorization in a tool of type mcp.
Sign in (OAuth) or Agent key (Authorization header)
Add GovConDash to Cursor's MCP settings and use it from the agent.
1Open ~/.cursor/mcp.json (or the project's .cursor/mcp.json), or open Customize in the sidebar to manage MCP servers.
2Add the govcondash entry below and save the file.
3Open Customize in the sidebar, make sure GovConDash is enabled, and sign in to your GovConDash Pro or Max account when prompted, unless you used the agent key entry.
4In the agent chat, ask a question that names GovConDash.
Sign in (OAuth) or Agent key (Authorization header)
Add GovConDash as an MCP server for GitHub Copilot's agent mode in VS Code.
1Open the Command Palette and run MCP: Add Server, choose HTTP, paste the server URL, enter govcondash as the server ID, and pick a destination such as Global (or add the entry below to .vscode/mcp.json).
2Review the trust and authentication prompts. VS Code opens the browser for you to sign in to your GovConDash Pro or Max account and choose Allow.
3In Copilot Chat, open Chat: Open Customizations, then Tools (or Configure Tools in the chat input), and confirm the GovConDash tools are on.
Sign in (OAuth) or Agent key (Authorization header)
Add GovConDash to a Copilot Studio agent as a Model Context Protocol tool.
1Open your agent in Copilot Studio, go to Tools, choose Add a tool, then New tool, then Model Context Protocol.
2Fill in Server name (GovConDash), Server description, and Server URL.
3For authentication choose OAuth 2.0 with the type Dynamic discovery, or API key with the type Header and the header name Authorization.
4Select Create (then Next), choose Create a new connection, sign in to your GovConDash Pro or Max account or enter Bearer followed by your agent key when prompted, and select Add to agent.
5Test the agent with a question.
Generative orchestration must be turned on for the agent to use MCP, and only the Streamable HTTP transport is supported. Copilot Studio creates a custom connector in your Power Platform environment; your environment's data policies must allow it.
Sign in (OAuth) or Agent key (Authorization header)
Add GovConDash to Cascade in Devin Desktop (formerly Windsurf) or to Devin's MCP settings.
1In Devin Desktop (formerly Windsurf), open the Actions menu at the top right of the Cascade panel, choose Open MCP config file in the MCPs section, and add the govcondash entry below.
2Refresh the MCP list and sign in to your GovConDash Pro or Max account if prompted, unless you used the agent key entry.
3In Devin, open Customize, then MCPs, then Add MCP, then Add custom MCP, choose HTTP, paste the server URL, and choose OAuth (then Connect) or Auth Header with the value Bearer followed by your agent key.
Sign in (OAuth) or Agent key (Authorization header)
Call GovConDash tools from a Zap or a Zapier agent through Zapier's MCP client.
1In Zapier, go to Apps, choose Add connection, and select MCP Client.
2Paste the server URL, choose Streamable HTTP as the Transport, and set OAuth to Yes, or set it to No and paste your agent key (the key alone) in Bearer Token.
3Choose Yes, Continue to MCP Client and sign in to your GovConDash Pro or Max account if prompted, then in a Zap add the MCP Client Run Tool action and pick a GovConDash tool.
4Test the step and turn the Zap on.
MCP Client is a beta feature in Zapier. With OAuth set to Yes, the Bearer Token field is ignored.
Agent key (Authorization header) or Sign in (OAuth)
Give an n8n AI Agent the GovConDash tools through the MCP Client Tool node.
1Add an AI Agent node to the workflow, then attach an MCP Client Tool node to its Tool input.
2Paste the server URL as the endpoint and, where your n8n version offers it, choose HTTP Streamable as the transport.
3Set Authentication to Bearer and create a credential holding your agent key (or use OAuth2 where your n8n version offers it).
4Under Tools to Include, choose All or the GovConDash tools you want, then run the workflow.
n8n's node documentation currently describes an SSE endpoint field only; the GovConDash server speaks Streamable HTTP, so use an n8n version whose MCP Client Tool offers that transport.
Not yet verified against the vendor's current documentation
Make
Agent key (Authorization header) or Sign in (OAuth)
Call GovConDash tools from a Make scenario or a Make AI agent through Make's MCP client.
1In a scenario, add the MCP Client app's Call a tool module.
2Choose Create a connection, select + New MCP Server, paste the server URL, and enter your agent key in API Key / Access token (or complete the OAuth sign-in).
Sign in (OAuth) or Agent key (Authorization header)
Any client that speaks Streamable HTTP can connect with the server URL and a sign-in or an agent key.
1Add a remote MCP server in your client and paste the server URL. The transport is Streamable HTTP.
2If the client supports OAuth, choose it: the client discovers the sign-in from the server's 401 challenge, registers itself (by dynamic client registration, or a client ID metadata document where supported), and opens the GovConDash sign-in for you to choose Allow.
3If the client takes a fixed header instead, mint an agent key on the Connected agents tab of your Account page and send it as Authorization: Bearer followed by the key.
The client must support remote MCP servers over Streamable HTTP. A client that only runs local servers cannot connect; one without OAuth needs an agent key in a header.
Check 2
An administrator permits it
Business and enterprise workspaces often turn custom connectors off by default. Ask the workspace owner to allow custom MCP servers, or to add GovConDash for the organization.
Check 3
It is the MCP URL, not this page
Paste the server URL shown at the top of this page. The documentation address (govcondash.ai/mcp) is not the server and will not connect.
Check 4
Keys never go into a conversation
An agent key belongs in the client's settings or an environment variable, never in a chat message. If a key was pasted anywhere else, revoke it on the Connected agents tab and mint a new one.