Orchestra MCP Server

Official

by orchestra-hq

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Get integration state

get_integration_state_for_state_aware

Read-only

Retrieve the saved state for a specified integration in the workspace your credential resolves to, enabling state-aware checks and reuse.

Instructions

Fetch the stored state for the given integration in the workspace the credential resolves to.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`integration`	Yes
`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 / 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_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"
-]New 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_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"
+]

First observedv0.1.0Sep 26, 2026

TDQS

B3/5.0

Behavior3/5

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

The readOnlyHint annotation already communicates that this is a safe read operation. The description adds useful scoping context about the credential-resolved workspace, but it does not disclose authentication requirements, rate limits, or what kind of state is returned beyond the output schema. With annotations covering safety, this is adequate but not rich.

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?

The description is a single, front-loaded sentence with no wasted words. It is efficient and easy to parse, though its brevity leaves some contextual gaps that could have been addressed without harming conciseness.

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

Completeness3/5

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

The output schema exists, so return values need not be explained, and the readOnlyHint annotation covers safety. However, the description does not provide usage guidance or help interpret the large integration enum, leaving gaps for an agent choosing among many sibling tools.

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

Parameters2/5

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

Schema description coverage is 50%, and the description does not compensate for the undocumented integration enum. It says only 'for the given integration,' which largely restates the required parameter, while the optional account parameter is already fully described in the schema. No additional syntax, format, or selection guidance is provided.

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 states a specific verb and resource: fetching stored state for a given integration. It also scopes the operation to the workspace resolved by the credential, which helps distinguish it from generic listing tools. However, it does not explicitly differentiate itself from sibling tools such as list_integration_connections or get_pipeline_data.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, nor any mention of alternatives or prerequisites. The agent can infer this is a read operation for integration state, but the description does not explain when to choose this tool over siblings or what conditions make it appropriate.

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

Deploy Server