Orchestra MCP Server

Official

by orchestra-hq

Overview Schema Source Related Servers Discussions Admin

Python

Remote

List integration connections

list_integration_connections

Read-only

Fetch all integration connections configured for your workspace, with optional filters by integration type or authentication status. Returns connection metadata only, never secrets.

Instructions

List the integration connections configured for the workspace the credential resolves to. Returns connection metadata only — secret auth parameters are never included in the response. Optionally filter by integration or authStatus.

Input Schema

TableJSON Schema

Name	Required	Description
`authStatus`	No
`integration`	No
`X-Orchestra-Account-Id`	No	Act 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

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Sep 30, 2026

changedInput schema / properties / integration / anyOf

Previous value: -[
-  {
-    "enum": [
-      "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_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",
-      "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",
-      "WEAVIATE",
-      "WEBHOOK",
-      "WELD",
-      "WINDOWS_SSH"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "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_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",
+      "WEAVIATE",
+      "WEBHOOK",
+      "WELD",
+      "WINDOWS_SSH"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv0.1.0Sep 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read, but the description adds genuine behavioral value: the result is scoped to the workspace the credential resolves to, and secret auth parameters are never returned. That return-content guarantee is not derivable from annotations or schema.

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

Conciseness4/5

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

Three short sentences, front-loaded with the scope and resource, then the safety guarantee, then the filters. Each sentence carries information; no filler or restatement of the title.

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?

With an output schema present the description need not explain return values, yet it still discloses the metadata-only guarantee. Workspace scoping and filtering are covered; the only gap is the absence of guidance on the account-override interaction, which the schema itself handles.

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 description coverage is only 33%, with the two filter parameters carrying no schema-level prose. The description names integration and authStatus as filters, which is useful, but adds nothing about how multiple filters combine or what the enum values mean.

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?

States a specific verb and resource (list integration connections) scoped to the credential's workspace, which is clear and actionable. It does not explicitly contrast itself with siblings such as get_integration_state_for_state_aware or list_accounts, so an agent must infer the boundary.

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?

The sentence 'Optionally filter by integration or authStatus' implies the intended usage context, but there is no explicit when-to-use vs. when-not guidance and no named alternative tool for related queries about integration state.

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

Deploy Server