MCP server for Airbyte connector building operations with AI ownership focus
Project description
connector-builder-mcp
Helping robots build Airbyte connectors.
Overview
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.
Key Features
- 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
Quick Start
Prerequisites:
- uv for package management (
brew install uv) - Python 3.10+ (
uv python install 3.10)
If you are developing or testing locally, you will also want to install:
- PoeThePoet as a task manager (
uv tool install poethepoet)
See the Contributing Guide or Testing Guide for more information about working with the repo locally.
Install:
The Poe sync and install commands are identical, giving a quick way to update your virtual environment or create one from scratch, if needed.
# These are identical:
uv sync --all-extras
poe install
poe sync
Run:
# You can use any of these to start the server manually:
uv run connector-builder-mcp
poe mcp-serve-local
poe mcp-serve-http
poe mcp-serve-sse
MCP Client Configuration
To use with MCP clients like Claude Desktop, add the following configuration:
Stable Version (Latest PyPI Release)
{
"mcpServers": {
"connector-builder-mcp": {
"command": "uvx",
"args": ["connector-builder-mcp"]
}
}
}
Development Version (Main Branch)
{
"mcpServers": {
"connector-builder-mcp": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/airbytehq/connector-builder-mcp.git@main",
"connector-builder-mcp"
]
}
}
}
Local Development
{
"mcpServers": {
"connector-builder-mcp": {
"command": "uv",
"args": [
"run",
"--project",
"/path/to/repos/connector-builder-mcp",
"connector-builder-mcp"
]
}
}
}
VS Code MCP Extension
For VS Code users with the MCP extension, use the included configuration in .vscode/mcp.json.
Contributing and Testing Guides
- Contributing Guide - Development setup, workflows, and contribution guidelines
- Testing Guide - Comprehensive testing instructions and best practices
Using Poe Tasks
For convenience, you can use Poe the Poet task runner:
# Install Poe
uv tool install poethepoet
# Then use ergonomic commands
poe install # Install dependencies
poe check # Run all checks (lint + typecheck + test)
poe test # Run tests
poe mcp-serve-local # Serve locally
poe mcp-serve-http # Serve over HTTP
poe mcp-serve-sse # Serve over SSE
You can also run poe --help to see a full list of available Poe commands.
If you ever want to see what a Poe task is doing (such as to run it directly or customize how it runs), check out the poe_tasks.toml file at the root of the repo.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file airbyte_connector_builder_mcp-0.1.0.tar.gz.
File metadata
- Download URL: airbyte_connector_builder_mcp-0.1.0.tar.gz
- Upload date:
- Size: 170.9 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.12.8
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
247a40a0a8c96ee24ea722225066179a092b8ede5954754dd6e0d1fa2d390817
|
|
| MD5 |
c5ed2c912b0e3ca4f0ad959a7fc9f8e5
|
|
| BLAKE2b-256 |
f5bdd8d8e0e5c3cc3019a8ea6e5f6e0cb28908507a29c7d9ee484d5652c7fda1
|
Provenance
The following attestation bundles were made for airbyte_connector_builder_mcp-0.1.0.tar.gz:
Publisher:
publish-command.yml on airbytehq/connector-builder-mcp
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
airbyte_connector_builder_mcp-0.1.0.tar.gz -
Subject digest:
247a40a0a8c96ee24ea722225066179a092b8ede5954754dd6e0d1fa2d390817 - Sigstore transparency entry: 364620180
- Sigstore integration time:
-
Permalink:
airbytehq/connector-builder-mcp@100d954d3740fa7de2933f589c84996795a20976 -
Branch / Tag:
refs/tags/v0.1.0 - Owner: https://github.com/airbytehq
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish-command.yml@100d954d3740fa7de2933f589c84996795a20976 -
Trigger Event:
push
-
Statement type:
File details
Details for the file airbyte_connector_builder_mcp-0.1.0-py3-none-any.whl.
File metadata
- Download URL: airbyte_connector_builder_mcp-0.1.0-py3-none-any.whl
- Upload date:
- Size: 17.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.12.8
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
3acf7b0a5b76a846885555316dc47d4ec0fd54cba8a0e0d4c8d8056382a03ad0
|
|
| MD5 |
6866a254aff97327eaf86d69f8033650
|
|
| BLAKE2b-256 |
437a97fcee7d5e30ee745da95b3a4551f31263f5c9bc4d3dd35b0e133f44e6a5
|
Provenance
The following attestation bundles were made for airbyte_connector_builder_mcp-0.1.0-py3-none-any.whl:
Publisher:
publish-command.yml on airbytehq/connector-builder-mcp
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
airbyte_connector_builder_mcp-0.1.0-py3-none-any.whl -
Subject digest:
3acf7b0a5b76a846885555316dc47d4ec0fd54cba8a0e0d4c8d8056382a03ad0 - Sigstore transparency entry: 364620189
- Sigstore integration time:
-
Permalink:
airbytehq/connector-builder-mcp@100d954d3740fa7de2933f589c84996795a20976 -
Branch / Tag:
refs/tags/v0.1.0 - Owner: https://github.com/airbytehq
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish-command.yml@100d954d3740fa7de2933f589c84996795a20976 -
Trigger Event:
push
-
Statement type: