Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

Update an integration connection

update_integration_connection

Update an integration connection's name, default status, credentials, or allowed environments. Use it to rotate auth parameters, reassign environment access, or change the credential store.

Instructions

Update one of connectionName, isDefault: true, allowedEnvironmentIds, or parameters with credentialStore on an integration connection. parameters follow the integration's authSchema and re-authenticate the connection; send obfuscated secrets back unchanged to keep them. allowedEnvironmentIds replaces the environments whose pipelines may use the connection, an empty list allowing every environment, and needs environment edit permission on every environment whose access changes. OAuth integrations return a redirectUrl instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "integration": "<integration>",
      "connection_id": "<connection_id>"
    },
    "name": "update_integration_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
isDefaultNo
parametersNo
integrationYes
callbackPathNo
connection_idYes
connectionNameNo
credentialStoreNo
validationParamsNoParameters matching the integration's validateSchema. Supplying them runs an extra validation against the provider once the connection authenticates.
allowedEnvironmentIdsNoEnvironments whose pipelines may use the connection. Empty means every environment.
X-Orchestra-Account-IdNoAct on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2026.11.13-0
    • addedInput schema / properties / allowedEnvironmentIds
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "format": "uuid4",
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Environments whose pipelines may use the connection. Empty means every environment."
      +}
    • changedInput schema / properties / integration / enum
      Previous value: -[
      -  "AIRBYTE_CLOUD",
      -  "AIRBYTE_SERVER",
      -  "AIRFLOW",
      -  "ARCH",
      -  "ALTERYX_SERVER",
      -  "ANTHROPIC",
      -  "AWS_EC2",
      -  "AWS_ECS",
      -  "AWS_EMR",
      -  "AWS_EKS",
      -  "AWS_FIREHOSE",
      -  "AWS_GLUE",
      -  "AWS_LAMBDA",
      -  "AWS_RDS",
      -  "AWS_REDSHIFT",
      -  "AWS_S3",
      -  "AWS_BATCH",
      -  "AWS_BEDROCK",
      -  "AWS_SAGEMAKER",
      -  "AWS_SECRETS_MANAGER",
      -  "AWS_SES",
      -  "AWS_STEP_FUNCTIONS",
      -  "AZURE",
      -  "AZURE_CONTAINER_APPS",
      -  "AZURE_DATA_FACTORY",
      -  "AZURE_DATA_LAKE_STORAGE",
      -  "AZURE_KEY_VAULT",
      -  "AZURE_KUBERNETES_SERVICE",
      -  "AZURE_LOGIC_APPS",
      -  "AZURE_SYNAPSE_ANALYTICS",
      -  "AZURE_VM",
      -  "BAUPLAN",
      -  "BOOMI",
      -  "CDATA",
      -  "CENSUS",
      -  "CLICKHOUSE",
      -  "COALESCE",
      -  "COUNT",
      -  "DATADOG",
      -  "DATABRICKS",
      -  "DATAPROC",
      -  "DATAZEN",
      -  "DBT",
      -  "DBT_CORE",
      -  "DLT",
      -  "DOMO",
      -  "DREMIO",
      -  "DUCKDB",
      -  "EMAIL",
      -  "ESTUARY",
      -  "ETLEAP",
      -  "FABRIC",
      -  "FABRIC_SYNAPSE",
      -  "FIVETRAN",
      -  "FORTRA",
      -  "GCP_BIG_QUERY",
      -  "GCP_CLOUD_RUN",
      -  "GCP_CLOUD_FUNCTIONS",
      -  "GCP_CLOUD_STORAGE",
      -  "GCP_DATAFLOW",
      -  "GCP_DATAFORM",
      -  "GCP_DATASTREAM",
      -  "GCP_LOOKER",
      -  "GKE",
      -  "GITHUB_ACTIONS",
      -  "GOOGLE_CLOUD",
      -  "HEVO",
      -  "HEX",
      -  "HIGHTOUCH",
      -  "HTTP",
      -  "HUBSPOT",
      -  "INFORMATICA_IICS",
      -  "INFORMATICA_POWERCENTER",
      -  "KAFKA",
      -  "KEBOOLA",
      -  "KLEENE",
      -  "LIGHTDASH",
      -  "LINUX_SSH",
      -  "MARIADB",
      -  "MATILLION",
      -  "MATILLION_ETL",
      -  "METAPLANE",
      -  "MICROSOFT_TEAMS",
      -  "MICROSTRATEGY",
      -  "MONGODB",
      -  "MOTHERDUCK",
      -  "MYSQL",
      -  "N8N",
      -  "NIMBLE",
      -  "NOTION",
      -  "OMNI",
      -  "OPEN_AI",
      -  "ORCHESTRA",
      -  "PARADIME",
      -  "PAGER_DUTY",
      -  "PINECONE",
      -  "PORTABLE",
      -  "POSTGRES",
      -  "POWER_AUTOMATE",
      -  "POWER_BI",
      -  "PREFECT_CLOUD",
      -  "PYTHON",
      -  "QLIK",
      -  "QLIK_REPLICATE",
      -  "QUICKBOOKS",
      -  "RENDER",
      -  "RIVERY",
      -  "RUDDERSTACK",
      -  "SALESFORCE",
      -  "SAP",
      -  "SFTP",
      -  "SHAREPOINT",
      -  "SIGMA",
      -  "SISENSE",
      -  "SLACK",
      -  "SNOWFLAKE",
      -  "SNOWPLOW",
      -  "SODA",
      -  "SQL_MESH",
      -  "SQL_SERVER",
      -  "STITCH",
      -  "STREAMKAP",
      -  "TABLEAU_CLOUD",
      -  "TALEND_CLOUD",
      -  "THOUGHTSPOT",
      -  "TOBIKO_CLOUD",
      -  "TYPESAFE",
      -  "WEAVIATE",
      -  "WEBHOOK",
      -  "WELD",
      -  "WINDOWS_SSH"
      -]New value: +[
      +  "AIRBYTE_CLOUD",
      +  "AIRBYTE_SERVER",
      +  "AIRFLOW",
      +  "ARCH",
      +  "ASTRATO",
      +  "ALTERYX_SERVER",
      +  "ANTHROPIC",
      +  "AWS_EC2",
      +  "AWS_ECS",
      +  "AWS_EMR",
      +  "AWS_EKS",
      +  "AWS_FIREHOSE",
      +  "AWS_GLUE",
      +  "AWS_LAMBDA",
      +  "AWS_RDS",
      +  "AWS_REDSHIFT",
      +  "AWS_S3",
      +  "AWS_BATCH",
      +  "AWS_BEDROCK",
      +  "AWS_CLOUDWATCH_LOGS",
      +  "AWS_SAGEMAKER",
      +  "AWS_SECRETS_MANAGER",
      +  "AWS_SES",
      +  "AWS_STEP_FUNCTIONS",
      +  "AZURE",
      +  "AZURE_CONTAINER_APPS",
      +  "AZURE_DATA_FACTORY",
      +  "AZURE_DATA_LAKE_STORAGE",
      +  "AZURE_FUNCTIONS",
      +  "AZURE_KEY_VAULT",
      +  "AZURE_KUBERNETES_SERVICE",
      +  "AZURE_LOGIC_APPS",
      +  "AZURE_SYNAPSE_ANALYTICS",
      +  "AZURE_VM",
      +  "BAUPLAN",
      +  "BOOMI",
      +  "CDATA",
      +  "CENSUS",
      +  "CLICKHOUSE",
      +  "COALESCE",
      +  "COUNT",
      +  "DATADOG",
      +  "DATABRICKS",
      +  "DATAPROC",
      +  "DATAZEN",
      +  "DBT",
      +  "DBT_CORE",
      +  "DLT",
      +  "DOMO",
      +  "DREMIO",
      +  "DUCKDB",
      +  "EMAIL",
      +  "ESTUARY",
      +  "ETLEAP",
      +  "FABRIC",
      +  "FABRIC_SYNAPSE",
      +  "FIVETRAN",
      +  "FORTRA",
      +  "GCP_BIG_QUERY",
      +  "GCP_CLOUD_RUN",
      +  "GCP_CLOUD_FUNCTIONS",
      +  "GCP_CLOUD_STORAGE",
      +  "GCP_DATAFLOW",
      +  "GCP_DATAFORM",
      +  "GCP_DATASTREAM",
      +  "GCP_LOOKER",
      +  "GKE",
      +  "GOOGLE_CHAT",
      +  "GITHUB_ACTIONS",
      +  "GITLAB",
      +  "GOOGLE_CLOUD",
      +  "HEVO",
      +  "HEX",
      +  "HIGHTOUCH",
      +  "HTTP",
      +  "HUBSPOT",
      +  "INFORMATICA_IICS",
      +  "INFORMATICA_POWERCENTER",
      +  "KAFKA",
      +  "KEBOOLA",
      +  "KLEENE",
      +  "LIGHTDASH",
      +  "LINUX_SSH",
      +  "MARIADB",
      +  "MATILLION",
      +  "MATILLION_ETL",
      +  "METAPLANE",
      +  "MICROSOFT_TEAMS",
      +  "MICROSTRATEGY",
      +  "MONGODB",
      +  "MOTHERDUCK",
      +  "MYSQL",
      +  "N8N",
      +  "NIMBLE",
      +  "NOTION",
      +  "OMNI",
      +  "OPEN_AI",
      +  "ORCHESTRA",
      +  "PARADIME",
      +  "PAGER_DUTY",
      +  "PINECONE",
      +  "PORTABLE",
      +  "POSTGRES",
      +  "POWER_AUTOMATE",
      +  "POWER_BI",
      +  "PREFECT_CLOUD",
      +  "PYTHON",
      +  "QLIK",
      +  "QLIK_REPLICATE",
      +  "QUICKBOOKS",
      +  "RENDER",
      +  "RIVERY",
      +  "RUDDERSTACK",
      +  "SALESFORCE",
      +  "SAP",
      +  "SFTP",
      +  "SHAREPOINT",
      +  "SIGMA",
      +  "SISENSE",
      +  "SLACK",
      +  "SNOWFLAKE",
      +  "SNOWPLOW",
      +  "SODA",
      +  "SQL_MESH",
      +  "SQL_SERVER",
      +  "STITCH",
      +  "STREAMKAP",
      +  "TABLEAU_CLOUD",
      +  "TALEND_CLOUD",
      +  "THOUGHTSPOT",
      +  "TOBIKO_CLOUD",
      +  "TYPESAFE",
      +  "WEAVIATE",
      +  "WEBHOOK",
      +  "WELD",
      +  "WINDOWS_SSH"
      +]
  2. Addedv2026.10.12-0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, it discloses that parameter updates trigger re-authentication, that obfuscated secrets must be sent back unchanged to preserve them, that allowedEnvironmentIds replaces access and requires edit permission on affected environments, and that OAuth integrations return a redirectUrl. This is strong behavioral context for a mutation tool, though it does not cover reversibility or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded: each sentence adds an actionable constraint or behavior, with no filler and no repetition of schema enum values.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, annotations, and existing output schema, the description provides enough context to perform most updates correctly, especially around secrets and environment access. It is not fully complete because callbackPath is unaddressed and some parameter semantics rely entirely on the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 30% across 10 parameters, and the description compensates for several key fields by explaining parameters, allowedEnvironmentIds, credentialStore, and secret handling. However, it leaves callbackPath entirely unexplained and does not clarify integration, connection_id, or the false case for isDefault.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Update) and resource (integration connection), and enumerates the updatable fields so the agent can distinguish this from create/delete/get siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful operational context for updating parameters and allowedEnvironmentIds, but does not explicitly state when to choose update vs create/delete/get, nor does it spell out prerequisites beyond the environment permission note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools