Contact Us
  • Home
  • Documentation
  • Core Weather API
  • MinuteCast™ API
  • Lightning API
  • Enterprise APIs
  • Pricing
  • FAQ
Company
  • Proven Superior Accuracy
  • About AccuWeather
  • Digital Advertising
  • Careers
  • Press
  • Privacy
  • Terms of Use
  • Brand Guidelines
  • Privacy Settings
Products & Services
  • For Business
  • For Partners
  • For Advertising
  • AccuWeather Enterprise APIs
  • AccuWeather Connect
  • Personal Weather Stations
Subscription Services
  • AccuWeather Premium
  • AccuWeather Professional
Apps & Downloads
  • iPhone App
  • Android App
  • See all Apps & Downloads

© 2026 AccuWeather, Inc.

xXfacebookFacebookinstagramInstagram
Quick-start guides
    Core weatherMinuteCast™
General
    AccuWeather APIsAuthenticationBest practicesAPI flow diagramData display formatsLanguages and localizationsUnit typesWeather iconsHTTP status codesGlossarySystem statusTerms of useBrand guidelines
Locations
    General informationLocation keysAdministrative areasRegions and countriesPoint-of-interest typesAutocomplete
Indices
    Index listDaily Index Categories and Level Values
Alerts
    Last actions
Alarms
    Thresholds
MCP server
    OverviewEndpoint and authenticationClient connectionToolsUsage and billing
MCP server

Endpoint and authentication

Your AI client needs two things: the server URL and your AccuWeather API key. One URL covers every tool.

Code
https://dataservice.accuweather.com/mcp

Get started by providing the server URL above and your API key. See client connection for instructions.

Authentication

Use the same key you use for the REST API. There is nothing extra to sign up for and no second credential to manage. Your keys are on the subscriptions page.

The key has to be on the free trial or the Elite plan. If something is wrong, your client will show one of these:

ResponseWhat it means
401 UnauthorizedThe key is missing, mistyped, or no longer active.
403 ForbiddenThe key works, but its plan does not include MCP. Compare plans on the pricing page.

Your assistant never sees the key

You enter the key once, in your client, and it authenticates the connection itself. The assistant using that connection cannot see your key, ask anyone for it, or repeat it back in a conversation.

Send the key

There are two methods to send your API key. Most clients provide a field for a header. In that case, use:

Code
Authorization: Bearer YOUR_API_KEY

Some clients only let you paste a URL, with nowhere to put a header. For those, add your key to the URL as an apikey parameter instead:

Code
https://dataservice.accuweather.com/mcp?apikey=YOUR_API_KEY

Either method works, but we recommend using the header when your client offers the option.

Treat a URL with your key in it as a secret

Including your API key directly in the URL means your API key is visible any time the URL is visible.

  • Do not commit it to a code repository, paste it into a ticket or chat, or include it in a screenshot.
  • Expect it to be recorded in browser history, server access logs, and proxy logs.
  • Rotate the key on the subscriptions page if a URL containing it gets out.

If your client asks for OAuth

Some MCP clients assume every remote server signs users in through OAuth, so they ask for a client ID and client secret, or try to open a sign-in page. AccuWeather uses an API key instead, so there is nothing to enter and no sign-in page.

If your client's guided setup requires OAuth, skip the setup and manually enter the server URL and header. See Client connection for help.

What next?

  • Client connection — setup examples for common MCP clients
  • Tools — what you can call once you are connected
  • Authentication — how API keys work across all AccuWeather APIs
Last modified on September 28, 2026
OverviewClient connection
On this page
  • Authentication
    • Send the key
    • If your client asks for OAuth
  • What next?