Rius

ai.glassflow由 glassflow.ai 發布v0.12.0更新於 Oct 27, 2026

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

已驗證Streamable HTTP可網頁執行安全與監控資料與分析AI 與機器學習

概覽

AI 產生的概覽

託管式 Rius MCP 伺服器，讓助理查詢 Rius 可觀測性平台中 AI 代理的追蹤、錯誤、成本、指標與告警。

可以做什麼
  • 檢視工作區與身分：目前使用者、工作區、使用者及使用者活動摘要
  • 瀏覽代理：列出代理、版本、版本比較與生命週期事件
  • 探索追蹤與跨度：追蹤摘要、追蹤清單、單筆追蹤、跨度與搜尋目錄
  • 檢視錯誤與指標：錯誤分組、工作區指標總覽與指標目錄
  • 讀取與管理告警：列出告警、規則與頻道，並建立、更新、刪除規則和頻道以及確認告警
  • 為工作區建立 API 金鑰
適用情境
當你的 AI 代理已將追蹤資料送到 Rius，並希望在編碼助理中直接詢問失敗、成本、延遲、版本差異或未處理告警時適用。也適合讓助理設定或調整告警規則的團隊。
執行需求
遠端 Streamable HTTP 端點，無需安裝或自行架設。需要一個已有代理追蹤資料的 Rius 工作區，以及 OAuth 2.1 瀏覽器登入，或在無瀏覽器情境下以 Authorization 標頭帶入 bearer 權杖形式的 Rius API 金鑰（例如使用 RIUS_API_KEY）。僅支援 stdio 的用戶端需透過 mcp-remote 之類的橋接。
安裝前請注意
寫入類工具會變更資料：可建立、更新或刪除告警規則與頻道、確認告警，並建立 API 金鑰。登入狀態下告警與金鑰工具需要組織管理員權限；API 金鑰預設為唯讀，除非授予 alerts:manage 或 channels:manage，且確認告警與建立金鑰在金鑰模式下永遠不可用。請將 API 金鑰視為機密，避免貼到共用設定中。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Rius，將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/ai.glassflow%2Frius/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "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.

來源：README.md，提交 e3ba244

工具

0
該伺服器需要登入，因此 SourceWeft 無法在沒有帳號的情況下讀取其工具，也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

2
  1. v0.12.0最新Oct 22, 2026
  2. v0.11.2Oct 21, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分