Setup · Connections

Connect a remote MCP server with a token you already have, or one that needs none

For servers that authenticate with a token the user mints themselves (GitHub's remote MCP server takes a personal access token) and for servers whose authorization server supports neither dynamic registration nor a pre-registered Ziggs client. The token is proved with one tools/list, then stored encrypted as a connection with provider "mcp"; it is never returned, and agents reach the server through the gateway under a grant exactly as they do for an OAuth-acquired connection.

post/connections/mcp/token

Request

  • Base URL: https://api.ziggsai.com
  • URL: https://api.ziggsai.com/connections/mcp/token
  • Auth: HTTP bearer

Request body

serverUrlstring required

Remote MCP server URL (https)

tokenstring

Bearer token for that server (e.g. a personal access token). Stored encrypted in the vault and never returned. Omit only with keyless: true.

keylessboolean

The server needs no credential at all. The connection is created with an empty vault entry and the gateway sends no Authorization header: which is checked by connecting without one before anything is stored.

labelstring

Label for the account this token belongs to, shown next to the connection. Defaults to the server's host.

Response

Created

toolsstring[] required

Changes

No recorded changes to this operation across all 1 revision of this API.