Helping robots build Airbyte connectors.
A Model Context Protocol (MCP) server for Airbyte connector building operations, enabling AI ownership of the complete connector development lifecycle - from manifest validation to automated testing and PR creation.
- Manifest Operations: Validate and resolve connector manifests
- Stream Testing: Test connector stream reading capabilities
- Configuration Management: Validate connector configurations
- Test Execution: Run connector tests with proper limits and constraints
To use with MCP clients like Claude Desktop, add the following configuration:
{
"mcpServers": {
"connector-builder-mcp--stable": {
"command": "uvx",
"args": [
"airbyte-connector-builder-mcp"
]
}
}
}For streamlined onboarding, the below config contains both a PyAirbyte MCP and Connector Builder MCP implementation.
{
"mcpServers": {
"airbyte-connector-builder-mcp": {
"command": "uvx",
"args": [
"airbyte-connector-builder-mcp"
]
},
"airbyte-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"--python=3.11",
"--from=airbyte@latest",
"airbyte-mcp"
],
"env": {
"AIRBYTE_MCP_ENV_FILE": "/Users/{YOUR-USER-ID}/.mcp/airbyte_mcp.env",
"AIRBYTE_CLOUD_MCP_SAFE_MODE": "1",
"AIRBYTE_CLOUD_MCP_READ_ONLY": "0"
}
}
}
}Important:
- Remember to update the
AIRBYTE_MCP_ENV_FILEpath to your actual path, and to create a new file there at that path. Note that the file can be empty to start. - For complete setup instructions and environment variable documentation, see the PyAirbyte MCP documentation.
For information on running from source, see the Contributing Guide.
The below MCP servers have been tested to work well with the Connector Builder MCP server and will complement its capabilities.
- Claude Code Users: You should only need the PyAirbyte MCP server for most tasks. Specifically, this enables publishing to Airbyte Cloud, running local tests, and validating manifests and configurations.
- Claude Desktop Users: As of this writing, Claude Desktop does not have built-in file system or timekeeping capabilities. Therefore, you will likely also want to add the Files Server MCP.
- Other Clients: Depending on your client, you may want to add the Timer MCP and/or the Playwright MCP for web browsing capabilities.
The PyAirbyte MCP Server (powered by PyAirbyte) gives the ability to publish and test connector definitions to your Airbyte Cloud workspace. It also includes tools for more extensive local tests, including syncing data locally to a cache and querying the results with SQL.
Note:
- Make sure to replace
/Users/{YOUR-USER-ID}/.mcp/airbyte_mcp.envwith the actual path to yourairbyte_mcp.envfile.- See below for details on the contents of this file.
- For information about the
AIRBYTE_CLOUD_MCP_SAFE_MODEandAIRBYTE_CLOUD_MCP_READ_ONLYenvironment variables, see the PyAirbyte MCP Safety documentation.
Your airbyte_mcp.env file should contain your Airbyte Cloud credentials:
# Airbyte Project Artifacts Directory
AIRBYTE_PROJECT_DIR=/path/to/any/writeable/project-dir
# Airbyte Cloud Credentials (Required for Airbyte Cloud Operations)
AIRBYTE_CLOUD_WORKSPACE_ID=your_workspace_id
AIRBYTE_CLOUD_CLIENT_ID=your_api_key
AIRBYTE_CLOUD_CLIENT_SECRET=your_api_secret
# Optional: Google Creds to Use for GCP GSM (Google Secret Manager):
GCP_GSM_CREDENTIALS_JSON={...inline-json...}For more detailed setup instructions, please see the PyAirbyte MCP docs.
If your agent doesn't already have the ability to read-write files, you can add this:
{
"mcpServers": {
// ... other servers defined here ...
"files-server": {
"command": "npx",
"args": [
"mcp-server-filesystem",
"/path/to/your/build-artifacts/"
]
}
}
}Playwright is the most common tool used for web browsing, and it doesn't require an API key and it can accomplish most web tasks.
{
"mcpServers": {
// ... other servers defined here ...
"playwright-web-browser": {
"command": "npx",
"args": [
"@playwright/mcp@latest",
"--headless"
],
"env": {}
}
}
}If you'd like to time your agent and it does not already include timekeeping ability, you can add this timer tool:
{
"mcpServers": {
// ... other servers defined here ...
"time": {
"command": "uvx",
"args": ["mcp-server-time", "--local-timezone", "America/Los_Angeles"]
}
}
}For VS Code users with the MCP extension, use the included configuration in .vscode/mcp.json.
- Contributing Guide - Development setup, workflows, and contribution guidelines
- Testing Guide - Comprehensive testing instructions and best practices
If you encounter bugs, have feature requests, or need help:
- Check Existing Issues: Search the GitHub Issues to see if your issue has already been reported
- Create a New Issue: If your issue is new, open an issue with:
- A clear, descriptive title
- Detailed description of the problem or feature request
- Steps to reproduce (for bugs)
- Expected vs actual behavior
- Your environment details (OS, Python version, MCP client)
- Relevant logs or error messages
- Community Support: For questions and discussions, you can also reach out through the Airbyte Community Slack
When reporting issues related to specific connectors or the Connector Builder UI itself, please file those in the main Airbyte repository instead.
In Claude Code, you can run /mcp to investigate your MCP Server configuration. This will also print the paths being used for the MCP JSON config.
If for any reason, /mcp does not find your servers, run /doctor to ensure the file can be parsed. If a parsing error is occurring, it will be noted in the /doctor output but not in the /mcp output.
{ "mcpServers": { // ... other servers defined here ... "airbyte-mcp": { "type": "stdio", "command": "uvx", "args": [ "--python=3.11", "--from=airbyte@latest", "airbyte-mcp" ], "env": { "AIRBYTE_MCP_ENV_FILE": "/Users/{YOUR-USER-ID}/.mcp/airbyte_mcp.env", "AIRBYTE_CLOUD_MCP_SAFE_MODE": "1", "AIRBYTE_CLOUD_MCP_READ_ONLY": "0" } } } }