mcp-airbyte-connector-status-query
Verifies the operational status of Airbyte data synchronization jobs and oversight of data flow processes. Enables streamlined administration of data pipelines via integration within the Claude Desktop environment.
Author

quintonwall
Quick Info
Actions
Tags
Overview
This demonstration application adheres to the Anthropic MCP specification. It is designed to function as an MCP server accessible within Claude Desktop, primarily facilitating user queries regarding the current state of Airbyte connections.
Setting Up Your MCP Server Instance
- Utilize 'uv' for isolated Python environment configuration.
-
Establish a dedicated virtual environment: bash uv venv source .venv/bin/activate
-
Install required packages from the manifest file: bash pip install -r requirements.txt
-
Provision a configuration file named
.envcontaining necessary Airbyte credentials: bash AIRBYTE_WORKSPACE_ID=xxx AIRBYTE_CLIENT_ID=xxx AIRBYTE_CLIENT_SECRET=xxx AIRBYTE_API_KEY=xxx -
Launch the service: bash uv run airbyte_status_checker.py
Configuring Claude Desktop for Server Access
- Specify the absolute filesystem paths for both 'uv' and the primary Python execution file within
claude_desktop_settings.json. The structure should resemble this:
"mcpServers": { "airbyte-status-checker": { "command": "/Users/quintonwall/.local/bin/uv", "args": [ "--directory", "/Users/quintonwall/code/airbyte-mcp-list-sources", "run", "airbyte_status_checker.py" ] } } }
- Integrate the newly configured server into Claude Desktop's active server registry. Navigate to the application settings, access Developer Settings, and select the '+' icon to introduce a new server endpoint. This action will reveal the location of your
claude_desktop_config.jsonfile. Insert the repository's content forclaude_desktop_config.jsoninto that file, then perform a restart of Claude Desktop. Successful registration is indicated by the appearance of a small hammer icon adjacent to the text input area.
Troubleshooting Guidance
If the claude_desktop_config.json file is correctly formatted, operational output is directed to ~/Library/Logs/anthropic/claude-desktop-server.log. Absence of log entries or the visibility of the hammer icon mandates a rigorous verification that your claude_desktop_config.json precisely mirrors the provided repository configuration and that all specified file paths are accurate.
