onyx_mcp_server (Resource)

An MCP server Onyx connects to, so its tools can be attached to agents.

Only servers that need no interactive sign-in can be managed here: NONE and API_TOKEN. An OAuth server is refused while the plan is built, because the flow needs a browser round-trip that Terraform cannot perform.

Which tools the server exposes is not part of this resource. Onyx learns them by calling the server, and both the tool selection and the Craft approval policies are rejected for a tool it has never seen.

Example Usage

# A public MCP server that needs no credentials.
resource "onyx_mcp_server" "docs" {
  name        = "Docs"
  description = "Public documentation search"
  server_url  = "https://mcp.example.com/mcp"
}

# A server behind one shared API token. Onyx returns the token masked, so the
# configuration is the only record of it: rotate it here, never in the UI.
resource "onyx_mcp_server" "weather" {
  name           = "Weather"
  server_url     = "https://weather.example.com/mcp"
  auth_type      = "API_TOKEN"
  auth_performer = "ADMIN"
  api_token      = var.weather_api_token

  # Only the Craft agent may reach this one.
  available_in_craft = true
  is_public          = false
}

# A server where every user supplies their own key. The template names the
# fields they fill in; admin_credentials are the applying admin's own values.
resource "onyx_mcp_server" "tickets" {
  name           = "Tickets"
  server_url     = "https://tickets.example.com/mcp"
  auth_type      = "API_TOKEN"
  auth_performer = "PER_USER"

  auth_template_headers = {
    "X-Api-Key" = "{api_key}"
  }
  admin_credentials = {
    api_key = var.tickets_admin_api_key
  }
}

Schema

Required

• name (String) Display name. Onyx does not require it to be unique, so two servers may share a name.
• server_url (String) URL Onyx calls the server on. Onyx refuses loopback and link-local addresses whatever the SSRF protection level, so a server on the Onyx host itself cannot be reached by name.

Optional

• admin_credentials (Map of String, Sensitive) Values for the auth_template_headers placeholders, required with auth_performer = "PER_USER" and rejected otherwise — a shared token is set through api_token. Onyx stores them against the identity that applied, not the server, and returns them masked.
• api_token (String, Sensitive) Shared API token, for auth_type = "API_TOKEN" with auth_performer = "ADMIN". Onyx returns it masked, so Terraform never reads it back: the configured value is the only record, and an imported server has none.
• auth_performer (String) Who supplies the credentials: ADMIN for one shared token, PER_USER for a token each user provides.
• auth_template_headers (Map of String, Sensitive) Headers Onyx sends to the server, for auth_performer = "PER_USER". A {placeholder} in a value names a field each user fills in. Onyx writes this itself for a shared token, and keeps whatever it holds when a request states none, so switching a server from per-user to a shared token leaves the per-user headers in place. Recreate the server to start over.
• auth_type (String) NONE or API_TOKEN.
• available_in_craft (Boolean) Whether the Craft agent may use this server. Onyx keeps this on a different endpoint from the rest, so setting it costs a second call.
• description (String) Free-text description.
• groups (Set of Number) User group ids that may use the server when it is not public. Onyx refuses the built-in Admin group here and asks for a public server instead. The configuration owns this list: removing it clears the groups on the server, including any added from the admin panel.
• is_public (Boolean) Whether every user may use the server. When false, only users and groups may.
• transport (String) STREAMABLE_HTTP or the deprecated SSE.
• users (Set of String) User ids (UUIDs) that may use the server when it is not public. The configuration owns this list: removing it clears the users on the server, including any added from the admin panel.

Read-Only

• id (String) Server id, assigned by Onyx.
• last_refreshed_at (String) When Onyx last listed the server's tools.
• owner (String) Identity that configured the server. For a Terraform run this is the API key's synthetic address, not a real mailbox.
• status (String) Connection state, which Onyx cycles on its own: CREATED, AWAITING_AUTH, FETCHING_TOOLS, CONNECTED or DISCONNECTED.
• tool_count (Number) How many tools Onyx has discovered on the server.

Import

Import is supported using the following syntax:

The terraform import command can be used, for example:

#!/bin/sh
# Import by numeric server id. Credentials are returned masked, so an imported
# server carries none: put api_token or admin_credentials back in the
# configuration before the next apply.
terraform import onyx_mcp_server.weather 3