[Aaron ("AJ") Steers (aaronsteers)]

Overview

👉 TL;DR: Tells agents which Cloud MCP tool to use for custom connectors versus connectors from the Airbyte registry. In prod telemetry, agents keep calling the registry-only deploy tool with custom connector names. Specifically, this changes only the tool descriptions: the deploy_connector_to_cloud docstring and its connector_name field, plus the publish_custom_source_definition docstring.

Changes

• deploy_connector_to_cloud docstring: says it works only for registry connectors, and for custom (YAML manifest) source connectors points to publish_custom_source_definition, or to list_custom_source_definitions and update_custom_source_definition when the definition already exists.
• deploy_connector_to_cloud connector_name field description: says it takes the canonical registry name, not a custom definition name or ID.
• publish_custom_source_definition docstring: points back to deploy_connector_to_cloud for registry connectors.

Why

In the last 24h of hosted Cloud MCP traffic, 4 deploy_connector_to_cloud calls failed with AirbyteConnectorNotRegisteredError. The connector_name values were custom connector names or a definition UUID. The tool descriptions never said which tool to use instead.

Test plan

• ruff format / ruff check on airbyte/mcp/cloud.py
• pytest tests/unit_tests/test_mcp_tool_utils.py tests/unit_tests/test_mcp_cloud.py tests/unit_tests/test_mcp_docs_includes.py tests/unit_tests/test_deferred_cloud_credentials.py: 270 passed

Link to Devin session: https://app.devin.ai/sessions/8fbdc1e4380941958b0bed24914614f2
Open in Devin Desktop: https://app.devin.ai/desktop/session/8fbdc1e4380941958b0bed24914614f2?variant=devin
Requested by: Aaron ("AJ") Steers (@aaronsteers)

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

Testing This PyAirbyte Version

You can test this version of PyAirbyte using the following:

# Run PyAirbyte CLI from this branch:
uvx --from 'git+https://github.com/airbytehq/PyAirbyte.git@devin/1791941748-custom-connector-tool-pointers' pyairbyte --help

# Install PyAirbyte from this branch for development:
pip install 'git+https://github.com/airbytehq/PyAirbyte.git@devin/1791941748-custom-connector-tool-pointers'

PR Slash Commands

Airbyte Maintainers can execute the following slash commands on your PR:

• /fix-pr - Fixes most formatting and linting issues
• /uv-lock - Updates uv.lock file
• /test-pr - Runs tests with the updated PyAirbyte
• /prerelease - Builds and publishes a prerelease version to PyPI

📚 Show Repo Guidance

Helpful Resources

• PyAirbyte Documentation
• API Reference

Community Support

Questions? Join the #pyairbyte channel in our Slack workspace.

📝 Edit this welcome message.

[github-code-quality]

Code Coverage Overview

Languages: Python

Python / code-coverage/pytest-no-creds

The overall line coverage in commit 65e42cd in the devin/1791941748-cus... branch is 79%. The line coverage in commit d9f652f in the release-candidate/v1 branch is 65%.

Show a line coverage summary of the most impacted files.

File	release-candidate/v1 d9f652f	devin/1791941748-cus... 65e42cd	+/-
airbyte/mcp/cloud.py	52%	83%	+31%
airbyte/_util/api_util.py	36%	68%	+32%
airbyte/cloud/connectors.py	34%	75%	+41%
airbyte/mcp/_datadog.py	0%	50%	+50%
airbyte/mcp/_user_identity.py	0%	93%	+93%
airbyte/_direct...ctors/models.py	0%	94%	+94%
airbyte/mcp/_telemetry.py	0%	94%	+94%
airbyte/mcp/_sso_auth.py	0%	96%	+96%
airbyte/cloud/models.py	0%	97%	+97%
airbyte/mcp/int...nc_status_ui.py	0%	97%	+97%

Python / code-coverage/pytest

The overall line coverage in commit 65e42cd in the devin/1791941748-cus... branch is 81%. The line coverage in commit d9f652f in the release-candidate/v1 branch is 71%.

Show a line coverage summary of the most impacted files.

File	release-candidate/v1 d9f652f	devin/1791941748-cus... 65e42cd	+/-
airbyte/cloud/connectors.py	51%	80%	+29%
airbyte/mcp/cloud.py	52%	83%	+31%
airbyte/mcp/_datadog.py	0%	50%	+50%
airbyte/mcp/int..._registry_ui.py	0%	92%	+92%
airbyte/mcp/_user_identity.py	0%	93%	+93%
airbyte/_direct...ctors/models.py	0%	94%	+94%
airbyte/mcp/_telemetry.py	0%	94%	+94%
airbyte/mcp/_sso_auth.py	0%	96%	+96%
airbyte/cloud/models.py	0%	97%	+97%
airbyte/mcp/int...nc_status_ui.py	0%	97%	+97%

Python / code-coverage/pytest-unit

The overall line coverage in commit 65e42cd in the devin/1791941748-cus... branch is 75%. Line coverage data for the release-candidate/v1 branch is not yet available.

Show a line coverage summary of the most covered files.

File	release-candidate/v1	devin/1791941748-cus... 65e42cd	+/-
airbyte/cloud/models.py	—	97%	—
airbyte/mcp/_sso_auth.py	—	96%	—
airbyte/_direct...ctors/models.py	—	94%	—
airbyte/cloud/client.py	—	90%	—
airbyte/exceptions.py	—	89%	—
airbyte/mcp/cloud.py	—	83%	—
airbyte/progress.py	—	80%	—
airbyte/cloud/connectors.py	—	75%	—
airbyte/_util/api_util.py	—	68%	—
airbyte/shared/...ql_processor.py	—	68%	—

---

_{Updated October 14, 2026 01:48 UTC}

[Aaron ("AJ") Steers (aaronsteers)]

Devin, check for newly merged tool updates for supporting custom connectors' pointers in these tools. Based on that, decide if this should be closed as no longer needed.

[devin-ai-integration]

Replaced by:

• feat(mcp): deploy sources from custom YAML definitions via deploy_connector_to_cloud #1387

Written by Devin