VS Code
Add your Plugsight MCP server to VS Code for Copilot agent mode, using an API key that VS Code stores securely.
VS Code can use your Plugsight accounts in Copilot agent mode. You connect it with your MCP server's URL and an API key.
What you need
- VS Code with Copilot agent mode.
- A Plugsight MCP server and its Server URL.
- An API key for that server.
Create an API key
- In Plugsight, open MCP servers and click your server.
- Under API key, click Create API key.
- Copy the key straight away. It isn't shown again.
Anyone with the key can use this MCP server's accounts. If it leaks, use Regenerate key or Revoke key on the server's page.
Connect VS Code
-
In your project, create or open the file
.vscode/mcp.json. -
Add this, replacing the URL with your Server URL:
{"inputs": [{"type": "promptString", "id": "plugsight-key", "description": "Plugsight API key", "password": true}], "servers": {"plugsight": {"type": "http", "url": "https://app.plugsight.app/mcp/YOUR_SERVER_ID", "headers": {"Authorization": "Bearer ${input:plugsight-key}"}}}} -
Save the file. VS Code asks for the key once and stores it securely. Paste the key you copied.
-
In Copilot agent mode, ask it to use the Plugsight tools, for example "List my connected Plugsight accounts."
Refresh after adding a new type of account
After you connect the first account of a new type (your first Zendesk, say), open VS Code's MCP settings and restart or reconnect the Plugsight server (or switch it off and on), then start a new chat. See Refresh the tools list.
Troubleshooting
It stopped working after I regenerated or revoked the key
What it means: the old key stopped working straight away.
How to fix it: create a new key on the server's page, then give VS Code the new key in place of the stored one.
The agent doesn't use my data
What it means: the agent didn't pick a Plugsight tool for your question.
How to fix it: ask it directly to use the Plugsight tools, for example "Using Plugsight, show last week's Google Ads spend".