Initializing the Utility

This utility represents a sample application adhering to the Anthropic MCP specification. It is engineered to execute as an MCP endpoint within Claude Desktop, primarily granting users the capability to query the current state of established Airbyte data connectors.

Setting Up the MCP Host Service

1. Implement uv for managing isolated Python execution environments.

2. Establish a dedicated virtual environment: bash uv venv source .venv/bin/activate

3. Load necessary package dependencies: bash pip install -r requirements.txt

4. Construct a .env configuration file containing the required Airbyte credentials: bash AIRBYTE_WORKSPACE_ID=xxx AIRBYTE_CLIENT_ID=xxx AIRBYTE_CLIENT_SECRET=xxx AIRBYTE_API_KEY=xxx

5. Initiate the application runtime: bash uv run airbyte_status_checker.py

Configuring the Client Application (Claude Desktop)

1. In the Claude Desktop configuration file (claude_desktop_settings.json), define the absolute pathways for both the uv executable and the primary Python script. The structure should closely resemble this example:

"mcpServers": { "airbyte-status-checker": { "command": "/Users/quintonwall/.local/bin/uv", "args": [ "--directory", "/Users/quintonwall/code/airbyte-mcp-list-sources", "run", "airbyte_status_checker.py" ] } } }

1. Integrate this newly defined service into the application's registered server roster. Navigate to the settings interface within Claude Desktop. Access Developer Settings and select the addition symbol ("+") to register a novel server endpoint. The interface will reveal the location of your primary configuration file (claude_desktop_config.json). Replace its contents with the configuration data supplied in this repository. A subsequent restart of Claude Desktop is required for activation. Successful registration is confirmed by the appearance of the designated toolkit icon (resembling a hammer) situated near the bottom-right quadrant of the text input area.

Troubleshooting Diagnostics

Assuming correct configuration within claude_desktop_config.json, operational output streams are directed to ~/Library/Logs/anthropic/claude-desktop-server.log. If log activity is absent, or if the toolkit icon fails to materialize, diligently verify that the content of your claude_desktop_config.json perfectly mirrors the reference material provided herein, paying close attention to all specified file system locations.