InBiot

This MCP server for InBiot provides real-time and historical air quality data, WELL Building Standard compliance tooling, and outdoor context to help you monitor, analyze, and improve indoor environments. It organizes access to device measurements, statistics, compliance checks, and health recommendations through a modular, easy-to-maintain setup that can export data and adapt to your environment.

How to use

You interact with the InBiot MCP server through an MCP client. Start by connecting your client to one or more MCP endpoints that you configure locally. Once connected, you can perform common tasks such as listing configured devices, retrieving current readings, pulling historical data with statistics, and running WELL compliance analyses. Use the tools to compare indoor vs outdoor conditions, generate health recommendations, and export historical data for external analysis.

How to install

Prerequisites: you need Python 3.10 or higher.

Option A — Easy Installation (Recommended) follow these steps.

git clone https://github.com/miguel-escribano/inBiot_MCP_with_WeatherAPI_and_WELL_standard.git
cd inBiot_MCP_with_WeatherAPI_and_WELL_standard

# Run interactive setup
python setup.py

Option B — Manual Installation

Clone the repository, install dependencies, and run the server.

git clone https://github.com/miguel-escribano/inBiot_MCP_with_WeatherAPI_and_WELL_standard.git
cd inBiot_MCP_with_WeatherAPI_and_WELL_standard

# Install with uv (recommended)
uv sync

# Or with pip
pip install -e .

Configure your devices

Create a configuration file from the example and tailor it to your environment.

cpy inbiot-config.example.yaml inbiot-config.yaml

Example configuration snippet

Use the following YAML to define your OpenWeather key (optional) and your InBiot devices. Replace placeholder values with your actual credentials and coordinates.

openweather_api_key: "your-key-here"  # Optional

devices:
  office:  # Device ID (any name you want)
    name: "Main Office"
    api_key: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
    system_id: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    latitude: 40.416775
    longitude: -3.703790

  lab:  # Add more devices as needed
    name: "Laboratory"
    api_key: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
    system_id: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    latitude: 40.416775
    longitude: -3.703790

Connecting your MCP client

Choose a client configuration that points to the MCP endpoint you run locally or remotely. The server supports standard stdio-based execution or a hosted HTTP endpoint if provided. For local execution, you typically start the server as a separate process and reference it from your MCP client configuration.

Configuration details and notes

The system supports YAML/JSON/ENV configurations with backward compatibility. Ensure the following are addressed: OpenWeather API key if you want outdoor data, correct device coordinates, and valid InBiot API keys and system IDs.

Troubleshooting

If the server has trouble connecting or you encounter rate limits, follow these steps.

1. Check the MCP logs in your IDE or console for error messages.

2. Verify that the absolute path to your installation is correct in your config.

3. Confirm the configuration file exists and is loaded (YAML, JSON, or ENV). Look for startup validation warnings.

4. Test starting the server manually with: python server.py or uv run python server.py to ensure the MCP initializes.

5. If you encounter API rate limits, wait for the retry window or space out requests per device.

Notes on upgrades and reliability

The server supports automatic retries with exponential backoff, respects 429 headers, and offers configurable retry counts and delays. Data exports and comprehensive statistics are available for deeper analysis.

Security considerations

Keep API keys and system IDs secure. Do not commit sensitive values to version control. Use environment variables or secured configuration management where possible.

Language and tooling

The server is implemented in Python and uses tooling that supports YAML/JSON configuration, tests, and modular skills for monitoring, analytics, compliance, and weather features.

Available tools

list_devices

List all configured InBiot devices.

get_latest_measurements

Retrieve real-time air quality data from a single or all devices.

get_historical_data

Fetch historical measurements for a device between two dates with optional aggregation.

well_compliance_check

Assess WELL Building Standard compliance for a specified device.

well_feature_compliance

Provide a feature-by-feature breakdown for WELL v2 features (A01-A08, T01-T07) with mitigation guidance.

health_recommendations

Generate actionable health and comfort recommendations based on current readings.

outdoor_snapshot

Get current outdoor weather and air quality data.

indoor_vs_outdoor

Compare indoor conditions to outdoor conditions for the selected device.

export_historical_data

Export historical data to CSV or JSON with optional aggregation.

get_data_statistics

Provide comprehensive statistical analysis and trend insights for a device.