MCP server

YouCORS MCP capabilities, access permissions, and connection instructions for Codex and Claude Code.

Model Context Protocol (MCP) lets an AI assistant work with an external service through named tools. Instead of copying connection details or logs into a chat, you can ask the assistant to retrieve the relevant records and explain them.

Endpoint and requirements

Connect your assistant to the YouCORS MCP server using Streamable HTTP:

https://api.youcors.com/mcp

You need a YouCORS account and an MCP client that supports OAuth, authorization-server discovery, and dynamic client registration. Sign in with your YouCORS account and approve the requested permissions. Management operations require an owner or administrator role in the target account.

MCP runs through the YouCORS API. You do not need to install an MCP server on your YCCaster machine. This URL is for your AI assistant; base stations and rovers use your caster's NTRIP host and port.

What the MCP integration can do

The server has tools for reading your account data and separate tools for making changes.

Inspect infrastructure and connections

Find your accounts, casters, servers, and caster instances. Inspect public addresses, ports, runtime versions, and reported service state.
Look up connection settings for a base station or rover: host, port, mount point, NTRIP version, credentials, and applicable access information.
List active and retained base or rover sessions. Inspect transferred bytes, the last status report, the last observed transfer, and the recorded end reason.
Read caster events and authentication results to investigate rejected connections.
List available cloud regions and server sizes before planning a deployment.

Connection-settings tools describe how to connect equipment. To find equipment that is actually connected, use session tools. An active session alone does not establish that corrections are flowing or that a rover has an RTK fix.

Manage infrastructure and access

With write permission and an owner or administrator role, the implementation supports:

Creating and deleting casters and cloud servers.
Creating, installing, and deleting caster instances, and applying their configuration.
Creating and deleting mount points; updating source credentials and connection permissions.
Creating, updating, revoking, and deleting NTRIP client credentials, including expiry dates and assigned account users.

Creating an instance and installing it are separate actions. Server provisioning runs in the background. Creating a server may incur charges and is subject to subscription limits. Applying instance configuration restarts YCCaster. Deleting a server, caster, or installed instance can stop active connections.

Revoking a client deletes its client record and prevents new authentication; it is not a command to terminate an already established session. Mount-point permissions apply to its owner, group, and other account users, rather than to an individual client ID. Changes to a mount point used by a relay can be blocked.

The MCP tool set does not currently provide billing changes, team invitations, relay configuration, or general shell access to a server.

Access and account data

The integration uses browser-based OAuth. A compatible client discovers the authorization server and registers itself; users do not need to create an API key or paste their account password into the assistant.

casters:read allows reading account data.
casters:write, together with casters:read, exposes management tools. Each change also checks the user's owner or administrator role in the target account.
Default authorization requests include both scopes. For a read-only integration, the client must request only casters:read before sign-in.

Read access can include base and rover credentials when their stored passwords are retrievable. Encrypted passwords are returned as unavailable, not decrypted. Authentication-attempt records omit the submitted password. Treat the assistant and its model provider as recipients of any data returned by the tools.

Review the requested permissions during authorization. Ask the assistant to show the target account, resources, and intended changes before it executes management tools. Client-side approval settings are separate from the server's OAuth permissions. You can review and revoke existing authorizations on the MCP connections page.

Connect Codex

With Codex CLI installed, register the HTTP endpoint:

codex mcp add youcors --url https://api.youcors.com/mcp
codex mcp login youcors
codex mcp list

Complete the browser sign-in, then start a new Codex session and use /mcp to inspect the connection.

For read-only authorization, sign out of any existing MCP authorization and request the read scope:

codex mcp logout youcors
codex mcp login youcors --scopes casters:read

Alternatively, configure the endpoint in ~/.codex/config.toml:

[mcp_servers.youcors]
url = "https://api.youcors.com/mcp"

Local Codex clients share MCP configuration on the same host. See the official Codex MCP instructions.

Connect Claude Code

With Claude Code installed, add a user-scoped HTTP server:

claude mcp add --transport http --scope user youcors https://api.youcors.com/mcp
claude mcp list

Start Claude Code, run /mcp, select youcors, and complete browser authentication. User scope makes the configuration available across your projects.

To request read-only access in a client version supporting oauth.scopes, use this entry in the project's .mcp.json, then authenticate from /mcp:

{
  "mcpServers": {
    "youcors": {
      "type": "http",
      "url": "https://api.youcors.com/mcp",
      "oauth": {
        "scopes": "casters:read"
      }
    }
  }
}

Use one configuration location for this server. See the official Claude Code MCP instructions.

Example requests

After connecting your account, try these requests. Replace the example names with your own.

List my accounts, then show the casters in the Survey Team account. Do not change anything.

Show the active rover sessions on BASE-01. Include when traffic was last observed, and flag missing status information.

Investigate why rover-07 cannot connect. Check recent authentication attempts, access expiry, and mount-point permissions. Explain the evidence before suggesting a fix.

Show the connection settings I should enter in my base station. Identify any password that is unavailable instead of guessing it.

Prepare a plan to add a rover client. Show the target account, caster, expiry date, and proposed changes. Wait for my approval before creating it.

If several accounts or similarly named resources match, ask the assistant to identify the intended one first. List results are paginated; a first page may not include every resource.

Troubleshooting

OAuth fails or the tool list is empty: check that you used https://api.youcors.com/mcp, completed browser sign-in, and have access to an active YouCORS account. Use the assistant’s MCP sign-in flow; a control-panel login token cannot replace MCP authorization.
A connection needs authentication: use the client's MCP sign-in flow. A control-panel session and an MCP authorization are separate.
Management tools are missing: check that the granted scopes include casters:write. A change also requires an owner or administrator role in that account.
A password is unavailable: the tool cannot recover a password stored in a non-retrievable form. An authorized credential reset is a separate operation.
A long-running operation times out: inspect the server or instance state before repeating a create, install, or delete request; the operation may already have started.

For more on managing your account, see Casters, Servers, and Sessions.