MCP Atlas Bb238a10

MCP运维云端

提供方 Deepesh-Katudia

运维云端 未标注 Token 社区 / 第三方

MCP Atlas 是一个用于多MCP系统的可观测性仪表盘,记录实时请求流、重建跟踪、测量延迟、跟踪服务健康状况、构建依赖图并检测异常。

一句话选型结论

按资料字段整理

MCP Atlas Bb238a10 属于运维云端类 MCP 服务器,传输方式未标注,Token,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式未标注 鉴权Token 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 4 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量4暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

可观测性TypeScript本地部署系统监控性能分析异常检测依赖图

安装与配置

未标注 Token
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 4 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 4 个工具,职责相对集中,接入后不容易误操作。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Atlas Bb238a10当前 4 未标注 未标注 无 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Deepesh-Katudia上游标注的维护方 Deepesh-Katudia
分类运维云端本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

9.7 KB
来自项目仓库与上游目录的原文,未做删改

MCP Atlas

MCP Atlas is an observability dashboard for multi-MCP systems. It records live request flows, reconstructs traces, measures latency, tracks service health, builds dependency graphs, and surfaces anomalies.

This repository currently supports two practical modes:

  • local live mode: Atlas proxies real HTTP requests across three lightweight MCP-like services
  • Blaxel integration mode: Atlas can connect to a Blaxel sandbox MCP endpoint and discover workspace MCP functions

Video Demonstration

https://github.com/user-attachments/assets/87a1d2d5-9ff5-4f31-92f7-3c10b5a88d16

What Is Implemented

  • live local services for Search MCP, Memory MCP, and File MCP
  • Atlas proxy that forwards requests and emits telemetry from real traffic
  • in-memory telemetry store with trace reconstruction
  • overview, topology, health, and logs pages
  • anomaly detection for failures, slow hops, slow traces, degraded services, and offline services
  • trace export from Logs as Excel-compatible CSV
  • Blaxel sandbox connection status endpoint
  • authenticated backend-side Blaxel MCP connector
  • Blaxel workspace MCP server discovery endpoint

Repository Layout

  • apps/server
    Atlas backend. Express + Socket.IO, telemetry aggregation, Atlas proxy routes, Blaxel integration.

  • apps/web
    React + Vite frontend dashboard.

  • functions/atlas-blaxel-mcp
    Deployable custom Blaxel MCP server exposing hosted Atlas tools over streamable HTTP.

  • services/search-mcp
    Lightweight local search service.

  • services/memory-mcp
    Lightweight local memory service.

  • services/file-mcp
    Lightweight local file service.

  • logs
    Runtime logs if you start background processes manually.

Architecture

Local Live Flow```text

Browser
|
v
MCP Atlas Web
|
v
Atlas Proxy (apps/server)
|
+--> Search MCP (4001)
+--> Memory MCP (4002)
+--> File MCP (4003)


Atlas proxy is the observability layer. It:

- receives requests
- assigns `traceId` and `requestId`
- forwards calls to downstream services
- measures latency
- records hop success or failure
- reconstructs traces
- streams dashboard snapshots over Socket.IO

### Blaxel Integration Flow```text
MCP Atlas Server
  |
  +--> Blaxel Sandbox API / SDK
  +--> Blaxel Sandbox MCP endpoint
  +--> Blaxel Workspace MCP function discovery API

Atlas currently uses Blaxel in three ways:

  • connect to or create a sandbox
  • connect to an authenticated sandbox MCP endpoint
  • list workspace MCP server functions from Blaxel
  • call a hosted custom Blaxel MCP function and record those requests as Atlas telemetry

Ports

Expected local ports:

  • 5173 web frontend
  • 4000 Atlas proxy/backend
  • 4001 Search MCP
  • 4002 Memory MCP
  • 4003 File MCP

Getting Started

Prerequisites

  • Node.js 22+
  • npm 11+

Install```bash

npm install


### Run Everything

From the repository root:```bash
npm run dev

This starts:

  • web on http://localhost:5173
  • Atlas proxy on http://localhost:4000
  • Search MCP on http://localhost:4001
  • Memory MCP on http://localhost:4002
  • File MCP on http://localhost:4003

Build```bash

npm run build


## Environment Variables

See .env.example.

Primary variables:

- `BL_API_KEY`
  Blaxel API key.

- `BL_WORKSPACE`
  Blaxel workspace name or ID.

- `BLAXEL_SANDBOX_NAME`
  Sandbox name to create or reconnect.

- `BLAXEL_SANDBOX_IMAGE`
  Sandbox base image.

- `BLAXEL_SANDBOX_MEMORY_MB`
  Sandbox memory in MB.

- `BLAXEL_SANDBOX_PORT`
  Exposed sandbox port.

- `BLAXEL_SANDBOX_REGION`
  Sandbox region.

- `BLAXEL_MCP_URL`
  Full MCP endpoint URL for the sandbox or hosted MCP server.

### Notes

- `.env` is gitignored.
- the backend explicitly loads the root `.env`
- the frontend uses Vite proxying to reach the backend during development

## Local Services

### Search MCP

Route:

- `POST /tool`

Example payload:```json
{
  "query": "alignment dashboard"
}

Memory MCP

Route:

  • POST /tool

Example payload:```json
{
"topic": "alignment dashboard",
"userId": "u1"
}


### File MCP

Route:

- `POST /tool`

Example payload:```json
{
  "filename": "atlas-notes.txt"
}

Forced failure payload:```json
{
"filename": "atlas-notes.txt",
"forceFailure": true
}


## Atlas Backend API

### Health and Snapshot

- `GET /health`
- `GET /api/snapshot`

### Local Service Registry

- `GET /api/services`

### Proxy Routes

- `POST /proxy/search-mcp`
- `POST /proxy/memory-mcp`
- `POST /proxy/file-mcp`

### Demo Flow

- `POST /api/demo/agent-task`

This produces a live multi-hop trace:

`Gateway MCP -> Search MCP -> Memory MCP -> File MCP`

### Blaxel Integration

- `GET /api/integrations/blaxel`
  Sandbox connection status.

- `GET /api/integrations/blaxel/mcp/ping`
  Server-side authenticated ping against the configured MCP endpoint.

- `GET /api/integrations/blaxel/mcp/tools`
  List tools from the configured Blaxel MCP endpoint.

- `POST /api/integrations/blaxel/mcp/tools/:toolName`
  Call a specific tool on the configured Blaxel MCP endpoint.

- `GET /api/integrations/blaxel/functions`
  List workspace MCP server functions from Blaxel.

- `GET /api/integrations/blaxel/functions/:functionName/test`
  Test-connect to a discovered workspace MCP function and list its tools.

- `GET /api/integrations/blaxel/functions/:functionName/tools`
  List tools exposed by a discovered or configured hosted Blaxel MCP function.

- `POST /api/integrations/blaxel/functions/:functionName/tools/:toolName`
  Call a hosted Blaxel MCP tool through Atlas and emit trace telemetry into the dashboard.

## Frontend Features

### Overview

- top-level metrics
- anomaly summary
- traffic trend chart
- alignment insights
- Blaxel MCP registry
- topology snapshot
- latest trace

### Topology

- dependency graph
- cluster toggle
- animated cluster view
- edge list

### Health

- service health table
- latency chart
- failure pressure view

### Logs

- recent traces list
- hop-by-hop trace detail
- export selected trace as Excel-compatible `.csv`

## Telemetry Model

Core event types:

- `HEARTBEAT`
- `REQUEST_RECEIVED`
- `REQUEST_FORWARDED`
- `REQUEST_COMPLETED`
- `REQUEST_FAILED`

Core fields include:

- `traceId`
- `requestId`
- `sourceMcp`
- `targetMcp`
- `eventType`
- `status`
- `latencyMs`
- `timestamp`
- `errorMessage`

All telemetry is currently stored in memory. There is no database yet.

## Anomaly Detection

Atlas currently raises anomalies for:

- failed traces
- slow hops
- slow end-to-end traces
- elevated p95 latency
- high failure rate
- offline services

These are computed in:

- apps/server/src/store.ts

## Blaxel Notes

### Why Browser Access to `/mcp` Returns 401

Blaxel MCP endpoints require authentication headers. Opening the MCP URL directly in a browser will return:```json
{
  "error": "Unauthorized",
  "message": "Authentication required"
}

That is expected.

Atlas solves this by connecting from the backend and sending:

  • Authorization: Bearer
  • X-Blaxel-Workspace:

Current Blaxel State

At the time of implementation:

  • sandbox MCP endpoint connection works
  • tool listing from sandbox MCP works
  • workspace function discovery endpoint works
  • Atlas can call a hosted Blaxel MCP function once it is deployed
  • workspace function list may be empty if no MCP functions are deployed in the workspace

If GET https://api.blaxel.ai/v0/functions returns an empty array for your workspace, Atlas will not treat the hosted MCP function as live even if a guessed URL exists. In that state, requests to the hosted endpoint commonly fail with Workload not found, which indicates the function was not deployed successfully on Blaxel.

Hosted Custom MCP Server

The repo now includes a deployable hosted MCP server at:

  • functions/atlas-blaxel-mcp/src/server.ts

It exposes four tools:

  • atlasSearch
  • atlasMemory
  • atlasFile
  • atlasAgentTask

Deployment config lives in:

  • functions/atlas-blaxel-mcp/blaxel.toml

Expected hosted endpoint after deployment:```text
https://run.blaxel.ai/<workspace>/functions/mcp-atlas-tools/mcp


Recommended deploy flow from that folder:```bash
bl serve --hotreload
bl deploy

After deployment, Atlas will discover mcp-atlas-tools from Blaxel or synthesize its expected URL from BLAXEL_ATLAS_FUNCTION_NAME and show it in the Blaxel MCP Registry.

Known Limitations

  • telemetry is in-memory only
  • no PostgreSQL or Supabase persistence yet
  • no auth layer on Atlas itself
  • local services are HTTP MCP-like services, not full MCP protocol servers
  • bundle size is still large on the frontend
  • Blaxel workspace discovery only lists deployed MCP functions; it does not itself generate traces
  • the Blaxel CLI is not installed in this environment, so deployment must be run from your machine after logging into Blaxel

Suggested Next Steps

  • persist traces and metrics in PostgreSQL or Supabase
  • add filtering and search across traces
  • ingest external real MCP traffic into the Atlas telemetry schema
  • unify local services, sandbox MCP tools, and workspace MCP functions into one observable registry
  • add richer per-tool telemetry for Blaxel MCP calls
  • reduce frontend bundle size with route-level code splitting

Useful Commands

Run all services:```bash
npm run dev


Build everything:```bash
npm run build

Run only backend:```bash
npm run dev -w @mcp-atlas/server


Run only frontend:```bash
npm run dev -w @mcp-atlas/web

Run only one service:bash npm run dev -w @mcp-atlas/search-mcp

File References

Main backend:
- apps/server/src/index.ts
- apps/server/src/store.ts
- apps/server/src/services.ts
- apps/server/src/blaxel.ts
- apps/server/src/blaxel-mcp.ts
- apps/server/src/blaxel-functions.ts

Frontend:
- apps/web/src/App.tsx
- apps/web/src/styles.css

Local services:
- services/search-mcp/src/index.ts
- services/memory-mcp/src/index.ts
- services/file-mcp/src/index.ts

常见问题

5 问
答案由本站依据条目字段整理,不引用上游原文
MCP Atlas Bb238a10 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

MCP Atlas Bb238a10 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

MCP Atlas Bb238a10 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Atlas Bb238a10 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

MCP Atlas Bb238a10 能提供哪些能力?

资料显示约 4 个工具;能力标签包括 可观测性、系统监控、TypeScript、性能分析。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。