Microsoft
GitHub Copilot CLI
Setup with your assistant
Copy this prompt into GitHub Copilot CLI. It guides the MCP setup, sign-in, and connection check.
Prefer to set it up yourself?
-
Check
copilot mcp list. If it already lists Valency, including through a plugin, do not add another connection. Otherwise run:Terminal window copilot mcp add --transport http valency https://mcp.valency.io/This saves Valency to your user-level Copilot CLI configuration.
-
Load the connection and sign in. If Copilot CLI is already open, exit it with
/exitand runcopilot --continuefrom the same terminal and directory to resume your conversation. Otherwise start it withcopilot. Complete Valency browser sign-in if it opens automatically. If Valency still needs authorization and no browser opens, enter/mcp auth valencyat the Copilot CLI prompt.A Valency account is created automatically on first sign-in. You do not need an API token, client ID, or secret, and your Valency email does not have to match your GitHub email.
-
Ask Copilot to call Valency's
list_sourcestool. A returned source list confirms that the agent can use the connection.copilot mcp listor/mcpshowing Valency only confirms configuration. -
Ask (more prompt ideas):
Use Valency to search for papers about quantum computing
Troubleshooting
Section titled “Troubleshooting”Tools don't appear after adding Valency?
Run copilot mcp get valency to check its status. Resume the conversation with copilot --continue so it loads the server. If it needs authorization, enter /mcp auth valency after Copilot has finished its current turn.
Need to start over with a direct connection?
Run copilot mcp remove valency, then follow the add and sign-in steps above. This removes a user-configured server, not one supplied by a plugin.
Need help?
Section titled “Need help?”If something isn't working, check Troubleshooting for common fixes. See the FAQ for general questions, or report an issue if you're still stuck.