Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

Get an integration connection

get_integration_connection
Read-only

Retrieve a single integration connection in the credential's workspace, including auth parameters; secret values are obfuscated.

Instructions

Fetch a single integration connection in the workspace the credential resolves to, including its auth parameters. Secret auth parameters are obfuscated in the response.

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": "get_integration_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
integrationYes
connection_idYes
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. Changed1 schema field changedv2026.11.13-0
    • 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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context: auth parameters are included and secret values are obfuscated in the response. It does not cover permission failures or missing-connection behavior, but it exceeds the annotation baseline.

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?

Two sentences, no wasted wording, with the core action and scope front-loaded. The secret-obfuscation note is placed where it is immediately relevant.

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?

An output schema exists, so return values need not be explained. The description covers the key behavioral caveat about secret obfuscation and the credential-scoped workspace, leaving only minor gaps such as error behavior.

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 33%, so the description should compensate, but it only clarifies the workspace/credential resolution context. The integration enum and connection_id remain self-explanatory from the schema, while X-Orchestra-Account-Id is already documented in detail in the schema.

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 gives a specific verb and resource: fetch a single integration connection. The word 'single' distinguishes it from list_integration_connections, though it does not name that sibling explicitly.

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?

Usage is implied by the read-only 'fetch a single connection' framing, and the credential/workspace scoping gives useful context. However, it does not state when to prefer this over get_integration, list_integration_connections, or get_integration_state_for_state_aware.

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