Connect GitHub Copilot CLI to Quest Portal
Add Quest Portal to the GitHub Copilot CLI with one command.
The address to use: https://mcp.questportal.com/mcp
Steps from the vendor's documentation. Menu names change, so if a step doesn't match what you see, look for the closest option or check GitHub's documentation: https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers
What you need
A Quest Portal account with Core or Pro, including the free trials. With Core your assistant can read your campaigns; with Pro it can also make changes.
GitHub Copilot CLI installed.
Set up
Step 1: Add the server. In a terminal, run:
Step 2: Sign in. Start Copilot CLI and run /mcp. If questportal shows that it needs sign-in, follow the prompt to open your browser.
Step 3: Approve access in Quest Portal. A Quest Portal page opens in your browser. Sign in if asked, check what Copilot is asking to use, and click Allow access.
Good to know
Check the connection with /mcp show questportal. Remove it with copilot mcp remove questportal.
On Copilot Business and Enterprise, an organization policy has to allow MCP servers.
You can install the Quest Portal plugin instead: copilot plugin marketplace add QuestPortal/plugins, then copilot plugin install questportal-plugin@questportal-plugins.
More help
See Connect Quest Portal to Claude and ChatGPT for what your assistant can do, what it can access and how to disconnect it. You can see and disconnect every connected assistant at https://app.questportal.com/settings/mcp.