UPPERBLUE

MCP / Guides

Connect an assistant with MCP

Set up the connection and complete sign-in with the appropriate Upperblue access.

Before you start

You need an MCP client supporting remote Streamable HTTP and appropriate Upperblue MCP permission. The account page manages MCP logins and access. Your ordinary website sign-in is distinct from an MCP login.

Use the public endpoint

https://mcp.upperblue.com/mcp

Choose the remote MCP connection option in your client and supply this URL. The setting name and location vary by client; use that product's current instructions for its interface.

Complete OAuth sign-in

  1. Set up an appropriate MCP login in Upperblue.
  2. Begin the connection in your client. The client discovers the sign-in service through public metadata.
  3. When the Upperblue sign-in page opens, use your MCP login.
  4. Return to the client and confirm that the tools are available.

OAuth is the primary path. You do not need to copy internal identifiers or sign-in URLs from technical metadata.

Keys for developer tools

A client supporting a custom header can use an MCP key in X-API-Key. Use an MCP key, not a REST API key. Store it in the client's secret settings, not a shareable configuration file. This does not replace OAuth for clients unable to send such a header.

Verify a first task

Discover a dataset and ask for a sourced, timed answer. If connection fails, use troubleshooting.