mcpField
B
BotnBot MCP

BotnBot MCP

Local
github.com/frocherData & Analytics0Updated 81w ago

About BotnBot MCP

BotnBot MCP is an MCP server for website operators who need to monitor availability, performance, and environmental impact. It provides metrics across several monitoring periods.

Key features

  1. 01Website availability monitoring
  2. 02Performance metrics
  3. 03CO₂ impact tracking
  4. 0424-hour, 7-day, and 30-day periods

Use cases

  1. 01Checking website health
  2. 02Reviewing performance over time
  3. 03Tracking website CO₂ emissions

MCP support

Exposes monitor listings and health, performance, and CO₂ metrics to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"botnbot_mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"build"
]
}
}
}
Run commanddocker run -i --rm build

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocibuild

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

BotnBot MCP

A Model Context Protocol (MCP) server implementation for monitoring website performance and environmental impact.

Features

  • Monitor website availability and performance
  • Track CO2 emissions and environmental impact
  • Get detailed metrics about website performance
  • Support for multiple monitoring periods (24h, 7d, 30d)

Installation

Local Installation
  1. Clone the repository:
git clone https://github.com/yourusername/botnbot_mcp.git
cd botnbot_mcp
  1. Install dependencies:
npm install
  1. Create a .env file with your configuration:
API_URL=your_api_url
API_TOKEN=your_api_token
Docker Installation
  1. Build the Docker image:
docker build -t botnbot_mcp .
  1. Run the container:
docker run -d \
  --name botnbot_mcp \
  -e API_URL=your_api_url \
  -e API_TOKEN=your_api_token \
  botnbot_mcp

Usage

Local Usage

Run the MCP server:

npm start

You can also provide configuration via command line arguments:

npm start -- --url "your_api_url" --token "your_api_token"
Docker Usage

Run the container with environment variables:

docker run -d \
  --name botnbot_mcp \
  -e API_URL=your_api_url \
  -e API_TOKEN=your_api_token \
  botnbot_mcp

Or with command line arguments:

docker run -d \
  --name botnbot_mcp \
  botnbot_mcp npm start -- --url "your_api_url" --token "your_api_token"

API Endpoints

  • GET /monitors - List all monitors
  • GET /monitor/:id/co2 - Get CO2 metrics for a specific monitor
  • GET /monitor/:id/health - Get health status for a specific monitor
  • GET /monitor/:id/performance - Get performance metrics for a specific monitor

License

This project is licensed under the MIT License - see the LICENSE file for details.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.