Model Context Protocol (MCP)

Connect your AI assistant to WindBorne to request weather data, work with webhooks, and read API documentation. Use this MCP server URL:

Available Endpoints

The MCP server exposes tools generated from WindBorne's API documentation. You control what your AI app can access through the API token you select and the permissions you approve.


Connect the MCP via OAuth

You can extend your WindBorne API access to AI apps and agents, including ChatGPT, Codex, Claude, and Claude Code, with OAuth in three simple steps.

  1. Add the MCP server to your AI app

    Add this URL in your AI app's MCP settings and choose OAuth if prompted:

    Your app can request access to read API data and view or manage your webhooks.

  2. Sign in to WindBorne

    Click Connect or Authenticate in your AI app. You'll be prompted to sign in if needed, and then redirected to WindBorne's authorization page.

  3. Select an API token and approve access

    Choose the API token the connection should use, review the requested access, and approve. You'll then be redirected to your AI app and all set to start using WindBorne tools.

Claude Code

Add the server from your terminal:

Shell

Open Claude Code, run /mcp , select the WindBorne server, and authenticate in your browser. See Claude Code's MCP instructions.

Codex

In the desktop app, open Settings → MCP servers → Add server. Choose Streamable HTTP, enter the server URL above, and save. Restart the connection if prompted, then select Authenticate. Leave bearer-token and authorization-header fields empty for OAuth.

With the CLI, add the server and sign in for read access:

Shell

To also manage webhooks, use --scopes api:read,api:webhooks-manage in the login command. See Codex's MCP instructions.

Other clients and custom harnesses

WindBorne supports client registration for agents and harnesses using Client ID Metadata Documents (CIMD), which let compatible apps identify themselves automatically. Claude, Codex, Claude Code, and ChatGPT already support this.

If your client does not support CIMD, use the manual API-token setup below.


Manual API-token setup

Use OAuth whenever possible. Manual API-token setup is retained for legacy clients and clients without CIMD support.

MCP for Claude Code

Use the Claude Code CLI to connect with header-based auth (no credentials in the URL).

  1. Set your API token as an environment variable

    Select your API token from the dropdown, then copy the command.

    Shell
  2. Add the WindBorne MCP server

    Use the environment variable from the previous step.

    Shell
  3. Test the connection

    Start Claude Code and ask something like "What's the weather in New York?" to verify connectivity.

MCP for Claude

In Claude, complete these steps:

  1. Access Connectors

    Open Customize → Connectors, or use the chat window’s Connectors menu to select Manage connectors.

  2. Add a Custom Connector

    In the Connectors panel, click the plus button and choose "Add custom connector".

  3. Configure the Connector

    Name the connector, select your API token from the dropdown below, then copy and paste the URL.

  4. Test the Connection

    Restart the application and test your first prompt.

MCP for Codex

This requires the Codex desktop app. Complete these steps:

  1. Open the Settings

    Click the settings field at the bottom left of the window and select the Settings option.

  2. Add MCP Server Details

    In the MCP servers tab, click Add server and configure a new server as Streamable HTTP with the following URL:

    Set WB_API_KEY as the Bearer token env var. Enter the variable name, not the token itself; the variable must be available to the Codex app’s process.

  3. Test the Integration

    Send a prompt to test the integration.

API Docs MCP

The same server provides public documentation tools without authentication:

  • read_api_docs : search and read API documentation by topic.
  • list_api_endpoints : see available API endpoints.

Connect using the server URL above to browse documentation. The server may list API tools before you sign in, but running API requests requires authentication. Documentation and connection-status tools remain available without signing in.