AQICN MCP Server

Created By
mattmarcina year ago
An MCP server to get Air Quality Data using AQICN.org
Overview

what is AQICN MCP Server?

AQICN MCP Server is a Model Context Protocol (MCP) server that provides air quality data tools from the World Air Quality Index (AQICN) project, allowing users to fetch real-time air quality data for cities and coordinates worldwide.

how to use AQICN MCP Server?

To use the AQICN MCP Server, install it via Smithery or manually set up your Python environment, configure your API key, and run the server to access air quality data.

key features of AQICN MCP Server?

  • Fetch air quality data for specific cities or coordinates.
  • Search for air quality monitoring stations by keyword.
  • Provides real-time air quality index (AQI) data.

use cases of AQICN MCP Server?

  1. Monitoring air quality in urban areas.
  2. Researching environmental data for academic purposes.
  3. Integrating air quality data into applications for public awareness.

FAQ from AQICN MCP Server?

  • What data can I retrieve using this server?

You can retrieve air quality data including AQI values, dominant pollutants, and station information.

  • Is there a cost to use the AQICN MCP Server?

The server is free to use, but you need to sign up for an API key from AQICN.org.

  • Can I use this server for commercial applications?

Yes, as long as you comply with the licensing terms.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattmarcin
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago