Cursor, VS Code and other apps

In these apps you paste your key into a configuration file; each app's file format is slightly different.

Where to find: The MCP configuration file of the app you use Who it's for: People using Cursor, VS Code, Gemini CLI or another MCP-speaking app In short: In these apps you paste your key into a configuration file; each app's file format is slightly different.

A key first

Every app on this page works with a key. If you do not have one: Creating a key

In the examples below, replace trz_mcp_live_... with your own key.

These files are plain text and your key sits in them in the clear. Do not share the file with anyone and do not push it to a repository.

Cursor

Configuration file: ~/.cursor/mcp.json (on Windows C:\Users\<your-user-name>\.cursor\mcp.json)

{
  "mcpServers": {
    "treyza": {
      "url": "https://api.treyza.co/mcp",
      "headers": {
        "Authorization": "Bearer trz_mcp_live_..."
      }
    }
  }
}

Save the file and restart Cursor. In Cursor's MCP settings screen you should see the treyza server as connected and the tools listed.

VS Code

Configuration file: .vscode/mcp.json inside your project

VS Code's format differs from Cursor's: the top-level key is servers and the type field is required.

{
  "servers": {
    "treyza": {
      "type": "http",
      "url": "https://api.treyza.co/mcp",
      "headers": {
        "Authorization": "Bearer trz_mcp_live_..."
      }
    }
  }
}

VS Code also lets you bind the key to a prompted value instead of writing it into the file ("Authorization": "Bearer ${input:treyza-key}"). That is the safer route if you want to keep your key out of a repository; VS Code's own documentation has the details.

Gemini CLI

Configuration file: ~/.gemini/settings.json

Here the address field is called httpUrl, not url.

{
  "mcpServers": {
    "treyza": {
      "httpUrl": "https://api.treyza.co/mcp",
      "headers": {
        "Authorization": "Bearer trz_mcp_live_..."
      }
    }
  }
}

Other apps

Any app that speaks MCP and lets you enter your own header can connect to Treyza. The app may name the fields differently; the three pieces of information you need are:

Field	Value
Server name	`treyza`
Address (URL)	`https://api.treyza.co/mcp`
Header	`Authorization: Bearer trz_mcp_live_...`
Transport	Streamable HTTP

In the panel, Settings → AI Access → Setup wizard → Other gives you these three lines with your key embedded, ready to copy.

My app does not let me enter a header — what now? Then it has to behave like an app that uses the consent-screen (OAuth) route. Treyza supports that route; see the flow on Claude Desktop and claude.ai. If your app supports neither route, it cannot connect to Treyza.

How do you know it works?

Ask in the app:

Which store are you connected to in Treyza?

If it writes your store's name, the connection is up. Next: Example scenarios

If it does not connect: Troubleshooting

The file formats on this page come from each app's own documentation dated 20.09.2026. Formats may change as the apps are updated; if in doubt, open the app's own MCP documentation — the three pieces on the Treyza side (address, header, transport) do not change.