Rius

ai.glassflowPublished by glassflow.aiv0.12.0Updated Oct 27, 2026

Query your AI agents' traces, errors, cost and alerts in Rius, the agent observability platform.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringData & AnalyticsAI & ML

Overview

AI-generated overview

Hosted Rius MCP server that lets an assistant query AI agent traces, errors, cost, metrics and alerts in the Rius observability platform.

What you can do
  • Inspect workspace and identity: current user, workspaces, users and user activity summaries
  • Browse agents: list agents, versions, version comparisons and lifecycle events
  • Explore traces and spans: trace summaries, trace lists, single traces, spans and search catalog
  • Review errors and metrics: error groups, workspace metrics overview and metrics catalog
  • Read and manage alerts: list alerts, rules and channels, plus create, update, delete rules and channels and acknowledge alerts
  • Create API keys for the workspace
When to use it
Useful when your AI agents send traces to Rius and you want to ask about failures, cost, latency, version differences or open alerts from a coding assistant instead of the console. Also fits teams that want an assistant to set up or adjust alert rules.
Requirements
Remote Streamable HTTP endpoint; nothing to install or self-host. A Rius workspace with agent traces, plus OAuth 2.1 browser sign-in or a Rius API key sent as a bearer token in the Authorization header (for example via RIUS_API_KEY) for headless use. Stdio-only clients need a bridge such as mcp-remote.
Before you install
Write tools change data: alert rules and channels can be created, updated or deleted, alerts acknowledged, and API keys created. Signed-in alert and key tools require an org admin; API keys are read-only unless granted alerts:manage or channels:manage, and acknowledge and key creation never work with a key. Treat the API key as a secret and avoid pasting it into shared configs.

Installation

In SourceWeft

  1. Open Rius in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.glassflow%2Frius/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "rius": {
      "type": "http",
      "url": "https://mcp.eu.console.rius-glassflow.com/mcp"
    }
  }
}

README

Rius MCP server

[Rius MCP connector]

Rius is an observability platform for AI agents, built by GlassFlow. The Rius MCP server lets your coding assistant query your agents' traces, errors, cost and alerts in plain language, from VS Code (GitHub Copilot), Claude Code, Cursor, Codex or any other MCP client.

This repository holds the public README for the hosted server, plus a reference copy of its server.json. The live registry entry is published by the server's release pipeline, so its version may be newer than the copy here. The server itself runs as a managed service; there is nothing to install or self-host.

  • Endpoint: https://mcp.eu.console.rius-glassflow.com/mcp
  • Transport: Streamable HTTP
  • Auth: OAuth 2.1 sign-in in the browser, or a Rius API key for headless use
  • MCP registry name: ai.glassflow/rius
  • Docs: https://docs.glassflow.ai/rius/mcp

What you can ask

Once connected, ask questions about your agents in the chat:

  • "Which of my agents had the most errors in the last 24 hours, and what are the top error groups?"
  • "Show me today's failed runs for support-agent and walk me through the worst one."
  • "Compare cost and latency between versions 1.4.0 and 1.5.0 of support-agent."
  • "Which end users cost the most this week?"
  • "List open alerts and explain what triggered each one."
  • "Create an alert that fires when checkout-agent error rate goes above 5%."

Prerequisites

A Rius workspace with agent traces in it. Sign up and follow the quickstart to send your first traces with the Rius SDK or any OpenTelemetry exporter.

Connect

Every client below uses the server name rius. On first use the client signs you in to Rius through the browser (some clients need a command to start it; see the per-client notes). The server supports dynamic client registration and client ID metadata documents, so there is no client ID to configure.

VS Code (GitHub Copilot)

Add the server to .vscode/mcp.json in your workspace (or your user mcp.json). Note the top-level key is servers:

json
{  "servers": {    "rius": {      "type": "http",      "url": "https://mcp.eu.console.rius-glassflow.com/mcp"    }  }}

Start the server from the Start action above its entry in mcp.json (or run MCP: List Servers) and allow the sign-in prompt. Then open Copilot Chat, switch to Agent mode and select the rius tools.

Claude Code

bash
claude mcp add --transport http rius https://mcp.eu.console.rius-glassflow.com/mcp

Run /mcp inside Claude Code to sign in.

Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

json
{  "mcpServers": {    "rius": {      "url": "https://mcp.eu.console.rius-glassflow.com/mcp"    }  }}

Then approve the server under Settings → MCP.

Codex

bash
codex mcp add rius --url https://mcp.eu.console.rius-glassflow.com/mcp

Other clients

Most clients accept a JSON block like this one:

json
{  "mcpServers": {    "rius": {      "type": "http",      "url": "https://mcp.eu.console.rius-glassflow.com/mcp"    }  }}

Clients that only support stdio can bridge through mcp-remote:

bash
npx mcp-remote https://mcp.eu.console.rius-glassflow.com/mcp

Per-client notes (Claude Desktop, Windsurf, Cline, Zed, Gemini CLI, opencode) are in the MCP server docs.

Headless use with an API key

For CI jobs, scripts or remote agents that cannot open a browser, send a Rius API key as a bearer token instead of signing in. Create a key with the Query data capability from the console's MCP page ("Connect an agent") or the Create API key dialog.

bash
export RIUS_API_KEY=...claude mcp add --transport http rius https://mcp.eu.console.rius-glassflow.com/mcp \  --header "Authorization: Bearer ${RIUS_API_KEY}"

In VS Code, let it prompt for the key once and store it securely:

json
{  "inputs": [    {      "type": "promptString",      "id": "rius-key",      "description": "Rius API key",      "password": true    }  ],  "servers": {    "rius": {      "type": "http",      "url": "https://mcp.eu.console.rius-glassflow.com/mcp",      "headers": {        "Authorization": "Bearer ${input:rius-key}"      }    }  }}

In other JSON configs, add a headers block. Not every client expands environment variables, so use your client's variable syntax or paste the key:

json
{  "mcpServers": {    "rius": {      "type": "http",      "url": "https://mcp.eu.console.rius-glassflow.com/mcp",      "headers": {        "Authorization": "Bearer ${RIUS_API_KEY}"      }    }  }}

In Codex, set bearer_token_env_var = "RIUS_API_KEY" on the server entry in ~/.codex/config.toml.

Tools

The main tools are below. The full, current reference with parameters is at https://docs.glassflow.ai/rius/mcp/tools.

AreaTools
Workspace and identityget_me, list_workspaces, list_users, user_activity_summary
Agentslist_agents, agent_versions, compare_agent_versions, agent_lifecycle_events
Traces and spansagent_traces_summary, list_agent_traces, get_agent_trace, list_spans, describe_search_catalog
Errors and metricsagent_error_groups, workspace_metrics_overview, list_metrics_catalog
Alerts (read)list_alerts, get_alert, list_alert_rules, list_alert_channels, describe_alert_catalog
Alerts (write)create_alert_rule, update_alert_rule, delete_alert_rule, create_alert_channel, update_alert_channel, delete_alert_channel, ack_alert
Keys (write)create_api_key

The tools marked "write" change data. When a call is not allowed, the server tells the assistant why instead of failing silently:

  • Signed in: read tools and ack_alert work for every member. Alert rule and channel tools, list_alert_channels and create_api_key need an org admin.
  • With an API key: a key is read-only unless it was created with alerts:manage (alert rule tools) or channels:manage (alert channel tools, including list_alert_channels). ack_alert and create_api_key never work with a key.

Links

License

The contents of this repository are released under the MIT License. The Rius service is governed by its own terms.

Source: README.md at commit e3ba244

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.12.0LatestOct 22, 2026
  2. v0.11.2Oct 21, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts