Guide

Connect your AI tool

Ask your AI tool about your vendors, projects and incidents. Connect the remote MCP server, authorize your organization, then check the results against your dashboard.

Connect with Claude Code

Add the remote HTTP server:

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

1. Open /mcp in Claude Code and select CheckUpstream.
2. Sign in to the correct organization.
3. Review the requested permissions and approve access.

The command uses user scope. See Claude Code's MCP documentation (opens in new tab) for project-scoped configuration and client-specific troubleshooting.

Connect another MCP client

Add a remote server with this URL in a client that supports HTTP and OAuth:

https://checkupstream.com/api/mcp/transport

{
  "mcpServers": {
    "checkupstream": {
      "url": "https://checkupstream.com/api/mcp/transport"
    }
  }
}

You do not need an API token for this connection. The client manages OAuth tokens; how it stores them depends on the client. Manage access in Settings → Credentials → AI Connections.

Verify the connection

Start with a read request that has an answer you can check against your dashboard:

• List my CheckUpstream projects and the vendors each depends on.Copy
• Show recent incidents for my monitored vendors, including source timestamps.Copy
• For the latest incident, separate vendor reports from measurements recorded by my app.Copy

Check that the organization and projects match your dashboard. For empty results, check the connected organization and whether it has repository or incident data.

Choose a task

Start with records you can check against your dashboard. A dependency relationship shows what to investigate; it does not prove application impact. Compare generated summaries with the source evidence.

Tool reference

These examples cover common tasks. Ask your client to list the tools available to your connection and show their required arguments.

Changes need a separate decision. For example, update_alert_config changes an alert rule, test_alert_config sends a test notification, and prepare_filing creates a claim draft. Write access and any required organization role still apply. Review the proposed action before approving it.

Claim tools prepare and record your work. They do not submit a claim to a vendor or establish that a credit is owed. You review and submit the claim; the vendor decides eligibility.

Prompts and resources

Your client's prompt picker can start an incident investigation or weekly reliability review. Prompts guide a workflow that can call several tools; review the results and any proposed changes.

Clients that support MCP resources can also open vendor, project and incident records directly. Use the client's resource list to find them.

Manage access

Revoke a connection you no longer use in Settings → Credentials → AI Connections. Tool calls share their arguments and returned records with the connected client. Review MCP data and audit records and the client's own data settings before sharing sensitive material.

Troubleshooting