API · MCP

Point an AI at the same data you use

NOTAMET runs an MCP server and a small set of REST endpoints. An agent can ask for the NOTAMs that matter to a flight, the weather around a point, or a full route briefing — and get an answer with the source and the licence attached.

Free with an account: 200 calls per day, shared by up to 5 keys.

The MCP server

Endpoint: https://notamet.com/api/mcp · transport: Streamable HTTP (JSON-RPC over POST). Five tools, no session, no streaming to configure.

Connecting a client

Claude Desktop, Cursor and any other MCP client: put the key in the header.

Claude Desktop — claude_desktop_config.json
{
  "mcpServers": {
    "notamet": {
      "type": "http",
      "url": "https://notamet.com/api/mcp",
      "headers": {
        "Authorization": "Bearer nm_live_TU_CLAVE"
      }
    }
  }
}
Cursor — .cursor/mcp.json
{
  "mcpServers": {
    "notamet": {
      "url": "https://notamet.com/api/mcp",
      "headers": { "Authorization": "Bearer nm_live_TU_CLAVE" }
    }
  }
}

The key is shown once, when you create it. If you lose it, revoke it in your account and create another.

Or plain HTTP

The REST endpoints stay open for one-off requests, rate limited by IP at 60 requests per minute.

Limits, and what this is not

Licence

Data derived from public aeronautical sources is published under CC BY 4.0. Every response includes the attribution line, so keeping it is all you have to do:

Attribution returned with every payload
Data: NOTAMET (notamet.com) · CC BY 4.0 · sources: ENAIRE/INSIGNIA, FAA NMS, NOAA/NWS AWC, EUROCONTROL EAD.

The licence covers the data, not the service: the code, the design, the editorial texts and the NOTAMET mark are reserved. We do not sell the data — we sell the tool.