Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

Create an integration connection

create_integration_connection

Creates a connection for an integration in your Orchestra workspace, storing its auth parameters and restricting which environments may use it.

Instructions

Create a connection for an integration in the caller's workspace. parameters must match the integration's authSchema, as returned by Get an integration. allowedEnvironmentIds restricts the connection to pipelines in those environments, and needs environment edit permission on every environment left out; omit it to allow every environment. Secret parameters are obfuscated in the response. OAuth integrations return a redirectUrl instead and need a user's credential.

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>",
      "connectionName": "<connectionName>",
      "parameters": "<parameters>"
    },
    "name": "create_integration_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYesAuth parameters, keyed by the field names in the integration's authSchema.
integrationYes
callbackPathNo
connectionNameYesDisplay name for the connection.
credentialStoreNoWhere the secrets live. ORCHESTRA stores them encrypted in Orchestra; an external store takes that store's reference parameters instead.ORCHESTRA
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: +{
      +  "default": [],
      +  "description": "Environments whose pipelines may use the connection. Empty means every environment.",
      +  "items": {
      +    "format": "uuid4",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • 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.1/5.0
Behavior4/5

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

Beyond the readOnlyHint=false/destructiveHint=false annotations, it discloses real behavior: secret parameters are obfuscated in the response, OAuth integrations return a `redirectUrl` and require a user credential, and restricting environments requires edit permission on every environment left out. That is meaningful disclosure of side effects and permission requirements; it stops short of stating whether duplicate connection names are rejected or how errors surface.

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 purpose leads, then prerequisites, then the environment restriction rule, then response behavior for secrets and OAuth. Every sentence conveys a distinct operational fact with no restatement of the tool name or schema.

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?

For an 8-parameter creation tool with nested objects and an output schema, the description covers the risky parts: auth parameter sourcing, environment scoping permissions, secret redaction, and the OAuth redirect flow. It omits the `callbackPath`/`credentialStore` interaction for OAuth flows, which is the one gap an agent could still hit.

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

Parameters4/5

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

With 75% schema coverage the baseline is 3, and the description adds genuinely new meaning: the coupling of `parameters` to the integration's `authSchema` and where to fetch it, plus the restriction/permission consequences of `allowedEnvironmentIds` and the default-to-all behavior when omitted. `callbackPath`, `validationParams`, and `X-Orchestra-Account-Id` are left to the schema, which already documents them.

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

Purpose4/5

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

The description opens with a specific verb and resource: "Create a connection for an integration in the caller's workspace." This clearly separates it from sibling tools like create_pipeline or get_integration_connection, though it never explicitly names an alternative tool for modifying or reading connections.

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

Usage Guidelines4/5

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

It states a concrete prerequisite: `parameters` must match the integration's `authSchema` as returned by "Get an integration", which routes the agent to that sibling before calling. It also explains when to omit `allowedEnvironmentIds` and flags the OAuth case that returns a `redirectUrl`, but it gives no explicit guidance on when to prefer an update versus a new create.

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