MetSci Support

MCP · Model Context Protocol

Connect your agent

Use the remote MCP server against your tenant on the MetSci LNS Console. Credentials are BYO bearer tokens; this MCP does not store operator passwords or global admin JWTs.

Canonical endpoints

Obtain tokens via your console’s sign-in flow (typically POST …/console/1.0/sign/in — see bootstrap JSON for shapes).

Open /metsci-console/info Doc: Connect MCP

Cursor (conceptual MCP config)

Add a Streamable HTTP MCP server targeting https://mcp.meteoscientific.com/metsci-console. Wire headers your client supports (Authorization, x-lns-base-url). 

{
  "mcpServers": {
    "metsci-console": {
      "url": "https://mcp.meteoscientific.com/metsci-console",
      "headers": {}
    }
  }
}

Populate headers with your bearer authorization per your tooling’s secret manager.

Claude Desktop (example)

If your Claude Desktop release supports MCP over HTTP/streaming, reuse the endpoint above in the vendor-recommended MCP config section. Older builds may still require stdio gateways — check Anthropic docs for HTTP MCP support versions. 

// Point your MCP launcher at 'https://mcp.meteoscientific.com/metsci-console'
// and attach Authorization headers at client runtime.

Packed token shape (mcpv1.<base64url>)

{
  "principal": "your-agent-label",
  "role": "self",
  "tenantScopes": ["TENANT-UUID"], // omit or "*" for operator tokens (carefully)
  "lnsBaseUrl": "https://console.meteoscientific.com",
  "chirpstackToken": "eyJ...",
  "consoleToken": "eyJ..."
}

Prefer short-lived JWTs & scoped tenants. Fail-closed LNS hostname allowlisting is enforced by default on the MCP worker — see the policy field at /metsci-console/info.

← MetSci Support home