Smarter Weather Developer Onboarding
RemoteAbout Smarter Weather Developer Onboarding
Smarter Weather Developer Onboarding is an MCP server and stdio bridge for coding agents setting up accounts on the Smarter Weather platform. It covers plan and documentation discovery, sign-up, API key handling, MCP configuration, and billing; weather data itself is provided by a separate service.
Key features
- 01Explore plans and platform documentation
- 02Sign up and start a trial
- 03Create, list, rotate, and revoke API keys
- 04Configure MCP clients
- 05Check usage and billing status
- 06Upgrade plans and open billing portal
Use cases
- 01Review platform plans before signing up
- 02Start a trial from an agent or CLI
- 03Set up API keys and MCP configuration
- 04Check usage or manage billing
MCP support
The package bridges stdio clients to the hosted Smarter Weather developer onboarding MCP server, with open discovery tools and optional OAuth-authenticated account tools. It can also configure an MCP client for the separate weather-data service.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.developers.smarterweather.comclaude mcp add --transport http smarterweather-onboarding https://mcp.developers.smarterweather.com{"mcpServers":{"smarterweather-onboarding":{"type":"http","url":"https://mcp.developers.smarterweather.com"}}}Open in Cursor{"servers":{"smarterweather-onboarding":{"type":"http","url":"https://mcp.developers.smarterweather.com"}}}Open in VS Code{"mcpServers":{"smarterweather-onboarding":{"type":"http","url":"https://mcp.developers.smarterweather.com"}}}{"mcpServers":{"smarterweather-onboarding":{"serverUrl":"https://mcp.developers.smarterweather.com"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
4This tool takes no parameters.
Details
From the project README@smarterweather/mcp-onboarding
stdio bridge to the Smarter Weather developer onboarding MCP server — the agent-first way onto the Smarter Weather platform. Your AI coding agent can explore plans and docs, sign you up, mint API keys, configure your MCP client, and manage billing, all from inside your editor.
A thin wrapper around mcp-remote with Smarter Weather defaults. Discovery and account tools run server-side. start_trial is answered locally: the package mints over HTTPS, writes SMARTERWEATHER_API_KEY to .env (mode 0600), and returns only a 12-character key_prefix. Via the stdio bridge, hosted create_api_key / rotate_api_key also sink into .env and strip the plaintext. After upgrading the package, restart the MCP server so the new interceptor is loaded.
CLI (no MCP host)
npx -y @smarterweather/mcp-onboarding@latest login # human present (device grant)
npx -y @smarterweather/mcp-onboarding@latest trial # no human (trial mint)
Both write .env and print only a key prefix. login blocks until the human approves — run it in the background or with a long shell timeout and relay the printed URL. Pass --json for a single whitelisted object.
Quick start (anonymous)
No account, no key, no auth. The open discovery tools (get_plans, get_documentation, sign_up) work immediately:
{
"mcpServers": {
"smarterweather-onboarding": {
"command": "npx",
"args": ["-y", "@smarterweather/mcp-onboarding"]
}
}
}
Authenticated mode (account tools)
Set SMARTERWEATHER_ONBOARDING_AUTH=required to unlock the account-scoped tools (create_api_key, list_api_keys, rotate_api_key, revoke_api_key, configure_mcp, get_usage, get_billing_status, upgrade_plan, open_billing_portal). The first request triggers an OAuth 2.1 + PKCE browser sign-in (Clerk); tokens cache at ~/.mcp-auth/.
Production Clerk keeps Dynamic Client Registration off. The bridge uses a pre-registered public PKCE OAuth client (client_id baked into the package) and pins the mcp-remote loopback callback to http://localhost:3334/oauth/callback so it matches the Clerk app’s redirect URI. No client secret is required or shipped.
{
"mcpServers": {
"smarterweather-onboarding": {
"command": "npx",
"args": ["-y", "@smarterweather/mcp-onboarding"],
"env": {
"SMARTERWEATHER_ONBOARDING_AUTH": "required"
}
}
}
}
Ensure port 3334 is free when authenticating; if mcp-remote falls back to a random port, Clerk will reject the redirect.
Configuration
| Env var | Default | Purpose |
|---|---|---|
SMARTERWEATHER_ONBOARDING_MCP_URL | https://mcp.developers.smarterweather.com | Target endpoint override (dev/staging). A positional URL argument takes precedence over both. |
SMARTERWEATHER_ONBOARDING_AUTH | (unset) | required → opt into the OAuth challenge and account-scoped tools. |
SMARTERWEATHER_ONBOARDING_OAUTH_CLIENT_ID | PQcxOLVZg5kxzhoC | Override the pre-registered Clerk OAuth client_id (staging / alternate apps). |
SMARTERWEATHER_ENV_FILE | (unset) | Absolute path for the local start_trial / CLI / proxy sink. When unset, the bridge uses the first MCP file:// root (skipping / and $HOME), then cwd/.env. CLI subcommands have no roots — they require this var or a non-guarded cwd. |
SMARTERWEATHER_API_KEY | (unset) | If already set, start_trial / trial / login / create sink are a no-op (already_configured) and do not mint. |
SMARTERWEATHER_API_BASE_URL | https://api.smarterweather.com | Override the trial/login key-api origin (dev/staging). |
Any extra CLI arguments (--debug, --transport http-only, --header X:y, …) pass through verbatim to mcp-remote. If you already pass a callback port or --static-oauth-client-info, the bridge will not double-inject them.
--version prints the bridge version plus the bundled mcp-remote version and exits.
Looking for weather data?
This package onboards you to the platform. The weather data itself is served by @smarterweather/mcp-weather (hosted at mcp.smarterweather.com) — which configure_mcp will happily set up for you.
License
Comments
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.