mcp-connect

Connect MCP

Updated 2026-05-27

Endpoint

• MCP (Streamable HTTP): https://mcp.meteoscientific.com/metsci-console
• Bootstrap JSON: https://mcp.meteoscientific.com/metsci-console/info
• Library index: https://mcp.meteoscientific.com/

Authentication (BYO token)

This MCP does not store your console password. You supply tokens from your LNS session.

1. Sign in to your console and obtain JWTs (typical pattern):

   POST https://YOUR_LNS_CONSOLE/console/1.0/sign/in

   Response fields often include chirpstackBearer and consoleBearer.

2. Call the MCP with either:

   • Raw bearer: Authorization: Bearer <jwt> plus header x-lns-base-url: https://YOUR_LNS_CONSOLE, or
   • Packed token: Authorization: Bearer mcpv1.<base64url(json)> where JSON includes lnsBaseUrl, chirpstackToken, optional consoleToken, optional tenantScopes.

Use HTTPS only in production. Host allowlisting is fail-closed by default (see /agents/ and worker metadata).

Cursor

Add an MCP server in Cursor settings (or project MCP config), pointing at:

https://mcp.meteoscientific.com/metsci-console

Provide headers for auth as your client allows (many expect env-based or config-based Authorization).

See /agents/ for a JSON snippet template.

Claude Desktop

In claude_desktop_config.json, add an MCP entry with URL transport if supported, or use a local bridge that speaks MCP over HTTP — check your Claude Desktop version for remote HTTP MCP support.

The canonical endpoint and bootstrap URL above are stable for tooling.

Privileged tools

Tools such as createTenant, generateApiKey, and topUpCredits are disabled unless the operator sets MCP_ENABLE_PRIVILEGED_TOOLS=true on the worker. Prefer narrow, tenant-scoped user tokens.

More detail

Full tool list and envelopes: GET https://mcp.meteoscientific.com/metsci-console/info

Machine-readable MCP summary: GET https://mcp.meteoscientific.com/metsci-console/llms.txt

← All docs