Skip to main content
VS Code’s chat connects to remote MCP servers over HTTP with custom headers. Its mcp.json format can prompt for your API key and store it securely, so the key never sits in the file.

Before you start

  • A Quotable API key from Settings → API keys. See Authentication.
  • VS Code with chat enabled.

Add the server

Create .vscode/mcp.json in your project:
.vscode/mcp.json
This file contains no secret, so you can commit it. Each teammate enters their own key.
The first time the server starts, VS Code asks you to trust it, then prompts for the key and masks what you type.

Check the connection

Run MCP: List Servers from the Command Palette and select quotable to start it, see its status or show its output. In the chat view, select Configure Tools to see the Quotable tools and turn individual tools on or off. Turn off run_agent if chat shouldn’t start agent runs. If the server fails to start with a 401, the key you entered is wrong, expired or revoked. Check the server’s output for the exact message and see Troubleshooting.

Try it

Open chat in agent mode and ask:
Chat picks the Quotable tools it needs. VS Code asks for confirmation before it runs a tool.
VS Code also reads portable MCP configuration files, .mcp.json at the workspace root and ~/.copilot/mcp-config.json, which use a top-level mcpServers object. This guide uses mcp.json with servers because it supports the masked key prompt.

Next steps

Example prompts

Ready-to-use questions for your workspace.

Workflows

Turn Quotable data into content briefs in your repo.

Tools reference

Inputs and outputs for each tool.
Last modified on November 18, 2026