Add the thirds.ai MCP server to VS Code

You add the thirds.ai MCP server to VS Code with one entry in mcp.json, and VS Code asks for your API key when the server starts. With thirds.ai, you save a design once, such as an invoice, a report, a certificate, or a post image, with your logo, colours, and fonts. Then you type in new details and get a finished PDF or image. Once VS Code has the server, you can ask GitHub Copilot chat for those files while you code, so you don't lay out each one by hand. Each finished PDF or image costs one credit, and a verified account gets 50 free credits a month.

See the VS Code file workflows for designs and prompts to try after setup.

Make it without code

You can make the same branded files in the thirds.ai editor without VS Code or any setup. It takes three steps, and you need a free thirds.ai account. The Feature announcement template is a good first try if you ship software, because you fill it in again for every release.

1. Open the Feature announcement template and click Use this template. Sign in and verify your account first if you need to.
2. Open the Data tab and type your product name, the version, the feature name, and the headline. Click Preview with data above the canvas to see the image. The preview is free.
3. Click Export, then Save and export PNG, and click Download image.

When you'd rather have Copilot make the next announcement from your release notes, add the thirds.ai MCP server to VS Code.

How do I add the thirds.ai MCP server to VS Code?

You add the thirds.ai MCP server to VS Code in three steps: create a key, open your mcp.json file, and add one server entry. You need a thirds.ai account and VS Code with GitHub Copilot chat. The entry uses a password input, so VS Code asks for the key and the key never sits in the file.

1. Create an API key on the API keys page.
2. Run MCP: Open User Configuration from the Command Palette.
3. Add this setup to mcp.json:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "thirds-api-key",
      "description": "thirds.ai API key",
      "password": true
    }
  ],
  "servers": {
    "thirds": {
      "type": "http",
      "url": "https://thirds.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${input:thirds-api-key}"
      }
    }
  }
}

The VS Code MCP configuration reference (checked 25 September 2026) says VS Code asks for an ${input:...} value the first time the server starts, then stores it securely. The password setting hides the key while you type it.

Your user mcp.json makes thirds.ai available in all your workspaces. To share the server with a project, put the same setup in .vscode/mcp.json in that project. Each person who opens the project then types their own key. The VS Code MCP server guide (checked 25 September 2026) also lists MCP: Add Server, which walks you through the same entry.

Check that VS Code sees the thirds.ai tools

You check the thirds.ai connection in VS Code with MCP: List Servers from the Command Palette. You need your API key ready to paste.

1. Run MCP: List Servers, select thirds, and start it.
2. Enter your API key when VS Code asks.
3. Open Chat, select Configure Tools, and turn on the thirds.ai tools you need.

If thirds doesn't start, run MCP: List Servers again, select thirds, and choose Show Output. A wrong key or a typo in the Authorization line shows up there.

Why are the thirds.ai tools missing in an Agent Host session?

The thirds.ai tools are missing in an Agent Host session because VS Code doesn't forward a server that asks for input, such as ${input:thirds-api-key}, to the Agent Host. The VS Code MCP server guide (checked 25 September 2026) states this rule. Use a local VS Code chat session for this setup.

Make your first file from VS Code

Your first file from VS Code starts with a plain request in Copilot chat. Ask it to list the thirds.ai tools, then ask for one file, such as "Make a feature announcement for version 4.3 from my Feature announcement template." VS Code can ask you to confirm each tool call, so you see what Copilot sends before it runs.

Read the main MCP guide before your first paid call. It explains credit approval, safe retries, and status checks.

FAQ

Where does VS Code save the API key?

VS Code treats a password input as secret input and stores it for later use. The key does not appear in mcp.json.

Can my team share one mcp.json file?

Yes. Put the setup in .vscode/mcp.json and commit it with the project. The file holds no key, so each person enters their own key the first time the server starts.

Does connecting spend credits?

No. Connecting and listing tools don't spend credits. AI template work and finished files can. Ask Copilot to show the action and the cost before it starts paid work.