Skip to content

πŸ› Bug: Coral MCP tries to install connectors before deploying a coral cloud destinationΒ #850

@aaronsteers

Description

Coral MCP tries to install connectors before deploying a Cloud destination. This can fail if the connector can't be installed, for instance if the Python version is a mismatch with the connector, or if PyAirbyte doesn't have a writeable directory.

Workarounds

First workaround is to ensure that the AIRBYTE_PROJECT_DIR env var is set as described here: https://docs.airbyte.com/ai-agents/pyairbyte-mcp#step-1-generate-a-dotenv-secrets-file

Second workaround is to use a CLI arg like --python=3.11 to ensure a compatible Python version is being used. Example here: https://docs.airbyte.com/ai-agents/pyairbyte-mcp#step-2-registering-the-mcp-server

Third workaround is to try to force Docker mode instead of Python. (Not well documented.)

Proposed Fixes:

The best fix is to skip installation when we are only creating the source or destination in order to deploy it to Cloud. (This might be implemented already for sources, and perhaps just destinations are not patched to leverage this pattern?)

Another fix option is to force Docker mode when we are running as MCP. I had thought this was already implemented, but the setting may not be correctly applied across both sources and destination use cases.

Docs: https://airbytehq.github.io/PyAirbyte/airbyte/mcp.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions