MCP clientsAI

Connect Zed to thirds.ai

Use with your agent

Give this prompt to your AI agent. The agent does the task for you.

Read https://thirds.ai/docs/mcp/zed and help me connect Zed to thirds.ai with an API key

Use Zed Agent to build templates and create PDFs or images. Create an API key on the API keys page first. Each successful PDF or static image costs one credit.

Install the server

Open Settings → AI → MCP Servers, click Add Server, and choose Add Remote Server. Zed writes an entry like this to your settings file:

JSON
{
  "context_servers": {
    "thirds": {
      "url": "https://thirds.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with your key. Zed sends header values exactly as written. It does not expand ${THIRDS_API_KEY} or ${env:THIRDS_API_KEY}. Restrict the settings file to your user, and do not commit the key. See Zed's MCP guide.

Leave OAuth unused. A remote server with no Authorization header starts Zed's OAuth flow, which thirds.ai MCP does not use.

Check the connection

On the MCP Servers page, the thirds indicator must be green. Ask Zed Agent to list the thirds.ai tools.

Read the main MCP guide before you start paid work.

FAQ

Why does Zed send Bearer ${THIRDS_API_KEY} as text?

Zed does not interpolate environment variables in MCP headers. Paste the real key in the Authorization value.

Where is the settings file?

Run zed: open settings file, or add the server from Settings → AI → MCP Servers so Zed writes the file.

Does connecting spend credits?

No. Connecting and listing tools don't spend credits. AI template work and successful renders can. Ask your agent to show the action and the cost before it starts paid work.

Ready to make your first file?

Start in the playground with a gallery template, or get an API key and send your first request from your own terminal.