Connect your assistant

Use this production server URL:

https://mcp.upty.io/mcp

Choose OAuth and Streamable HTTP wherever the client asks for authentication and transport. Upty's MCP connection uses OAuth; an ordinary upk_ API key, a host token, a log token or a OneUptime Core key is not a substitute.

Approve access in UptyCopy Anchor Link

The client opens your browser on Upty's sign-in and consent flow:

1. Sign in with your existing Upty method.
2. Review the requesting app's name, client identifier and return address. The name alone does not establish who owns an app.
3. Select the workspace that the assistant may use.
4. Choose Read-only or Full access, then select Allow access.
5. Return to the client and check its MCP connection status.

Read-only is selected initially. Full access is available only when the client requests management scope and your role permits management operations. You can grant less access than a client requests; you cannot grant more than your role allows.

Claude CodeCopy Anchor Link

Install the public pluginCopy Anchor Link

claude plugin marketplace add uptyio/mcp
claude plugin install upty@upty

Restart Claude Code if prompted. Open /mcp, choose upty and authenticate. The plugin supplies the endpoint and workflow skills; it contains no API token.

Connect without the pluginCopy Anchor Link

claude mcp add --transport http --scope user upty https://mcp.upty.io/mcp

The --scope user setting makes the connection available outside the current project. Open /mcp in Claude Code to authenticate and inspect the result. Use either the plugin or the direct server entry to avoid duplicate Upty connections in the client.

Native clients may receive OAuth callbacks on a temporary loopback port. Upty accepts HTTP callbacks on localhost, 127.0.0.1 or [::1] under the registered loopback callback rules; those host names are not interchangeable. Do not edit the return URL generated by the client. See callback troubleshooting.

CodexCopy Anchor Link

The installed CLI's remote-server and OAuth commands are:

codex mcp add upty --url https://mcp.upty.io/mcp
codex mcp login upty

To request management scope explicitly for a login:

codex mcp login upty --scopes mcp:read,mcp:write,offline_access

Upty still asks for approval and defaults to Read-only. Select Full access only if you want that connection to manage resources.

You can also set the server URL in config.toml and authenticate through the client's MCP controls:

[mcp_servers.upty]
url = "https://mcp.upty.io/mcp"

These are setup instructions, not a claim that every Codex release or account configuration has been end-to-end certified with Upty. Check your installed codex mcp --help and OpenAI's MCP documentation when its configuration differs.

ChatGPTCopy Anchor Link

Where your account and organization permit custom MCP servers, open ChatGPT's plugin/custom MCP setup, enter the Upty server URL and choose OAuth. Create the connection, sign in to Upty, select the workspace and access level, and approve.

OpenAI documents this under Add custom MCP server. Its current flow uses ChatGPT Plugins → Add custom MCP server; labels and availability can change. Adding Upty yourself is different from installing an OpenAI-reviewed marketplace listing. Upty does not require you to paste a static OAuth client secret into its public plugin.

Claude web, desktop and other clientsCopy Anchor Link

Use the client's custom connector or remote MCP settings, enter the same server URL and follow OAuth. Some organizations require an administrator to enable custom connectors first. Use the client's current documentation for exact controls rather than copying another client's JSON configuration.

Clients limited to local stdio servers or fixed API-key headers need an OAuth-capable remote MCP connection method. Upty does not provide a token-copy setup as an alternative to its OAuth consent flow.

Verify and manage the connectionCopy Anchor Link

Start with a read request such as:

List my monitors and show their current states. Do not change anything.

In Integration & API, MCP · Connected apps lists the app, client identifier, workspace, approved scope, connection date, latest use and expiry. Disconnect removes that connection's access. To change workspace or access level, disconnect and reconnect from the client.

For development, use https://mcp.uptiva.linuxmaster.cloud/mcp under a distinct client name such as upty-dev; it has separate sign-in and data.