@kapa.ai I use a self-hosted airbyte instance. Can I use aribyte agents?

Based on the available knowledge sources, Airbyte Agents and self-hosted Airbyte are two separate products. Airbyte Agents is a standalone cloud platform available at app.airbyte.ai — it's not an add-on to a self-hosted Airbyte instance. It has its own plans (Free, Individual, Team, Custom) and provides AI agents with real-time access to business data via managed connectors, credential storage, and a Context Store. [What is Airbyte Agents] Importantly, the documentation notes: > Agent connectors don't replace existing source and destination connectors. They complement them by providing agents with real-time access to the same systems. [Agent connectors] So in practice: • You can sign up for Airbyte Agents independently at app.airbyte.ai — no self-hosted instance required or integrated. • Your self-hosted Airbyte instance (for data replication) is unrelated to the Airbyte Agents platform. The knowledge sources do not explicitly state whether Airbyte Agents can be pointed at or integrated with a self-hosted Airbyte deployment. For a definitive answer on this, I'd recommend reaching out to the Airbyte community or support via the Airbyte Slack. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

@kapa.ai Ok, so I can't use an mcp server to check my airbyte instance (connectors, jobs, logs...)

Actually, there is an Airbyte Replication MCP server that could be relevant here, but with some caveats. The Airbyte Replication MCP server (powered by PyAirbyte) allows you to manage Airbyte replication workflows through MCP-compatible clients. It supports things like listing connectors, validating configurations, and running sync operations. [Replication MCP] However, looking at the setup instructions, the environment file references Airbyte Cloud credentials specifically:

AIRBYTE_CLOUD_CLIENT_ID=your_api_key
AIRBYTE_CLOUD_CLIENT_SECRET=your_api_secret
AIRBYTE_CLOUD_WORKSPACE_ID=your_workspace_id

[Getting Started] The knowledge sources do not explicitly confirm whether the Replication MCP server supports connecting to a self-hosted Airbyte instance for checking jobs, logs, and cloud-managed connectors. There is also a

airbyte.mcp.local

sub-module which handles local connector operations (not the same as managing your self-hosted instance). [Local MCP] For a definitive answer on self-hosted support, I'd recommend checking the PyAirbyte GitHub Discussions or opening an issue on PyAirbyte GitHub Issues. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements