MCP E52ce37d

MCPAI代理

提供方 未标注

AI代理 SSE · 服务端推送 会话登录 社区 / 第三方
查看接入方式

全面解析MCP Redfish GoMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,MCP Redfish Go能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

MCP E52ce37d 属于AI代理类 MCP 服务器,SSE · 服务端推送,会话登录,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式SSE · 服务端推送 鉴权会话登录 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

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

能力标签

安装与配置

SSE · 服务端推送 会话登录
早期远程传输方式,正在被 HTTP 取代
npx @modelcontextprotocol/inspector /path/to/bin/redfish-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP E52ce37d当前 未标注 SSE · 服务端推送 远程部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式SSE · 服务端推送早期远程传输方式,正在被 HTTP 取代
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

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

Redfish MCP Server (Go)

A high-performance MCP (Model Context Protocol) server implementation in Go for interacting with Redfish-enabled infrastructure. This server provides AI agents and applications with natural language access to Redfish API endpoints, enabling intelligent management and monitoring of data center infrastructure.

Overview

The Redfish MCP Server enables AI-driven workflows to interact with Redfish-compliant servers through natural language queries. It provides a standardized interface for accessing hardware information, sensor data, and management capabilities of modern infrastructure components.

Key Features

  • 🚀 High Performance: Native Go implementation with compiled binaries and low memory footprint
  • 🔍 Redfish API Integration: Full support for Redfish v1.x API specifications
  • 🤖 MCP Compatible: Seamless integration with MCP clients and AI assistants
  • 🔐 Secure Authentication: Support for Basic and Session-based authentication
  • 🌐 Multiple Transports: stdio, SSE, and streamable-http transport options
  • 🔄 Concurrent Operations: Goroutine-based concurrent discovery and requests
  • 📊 Structured Data Access: JSON-based resource data retrieval with headers
  • 🛠️ Extensible Architecture: Modular design for easy customization

Quick Start```bash

Clone the repository

git clone https://github.com/theoriginalaiexplorer/mcp-redfish-go.git
cd mcp-redfish-go

Build the server

go build -o bin/redfish-mcp ./cmd/redfish-mcp

Configure environment

export REDFISH_HOSTS='[{"address": "192.168.1.100", "username": "admin", "password": "secret"}]'

Run the server

./bin/redfish-mcp


## Installation

### Prerequisites

- Go 1.21 or later
- Access to Redfish-enabled infrastructure

### Building from Source```bash
# Clone the repository
git clone https://github.com/theoriginalaiexplorer/mcp-redfish-go.git
cd mcp-redfish-go

# Initialize Go module
go mod tidy

# Build for your platform
go build -o bin/redfish-mcp ./cmd/redfish-mcp

# Or build for multiple platforms
make go-build-all

Pre-built Binaries

Download the latest release binaries from the Releases page for:
- Linux (amd64)
- macOS (amd64)
- Windows (amd64)

MCP Tools

The server provides two primary MCP tools for interacting with Redfish infrastructure:

list_servers

Lists all configured Redfish servers that can be accessed.

Example usage:```
List all available Redfish servers


**Response:**```json
{
  "servers": ["192.168.1.100", "192.168.1.101"]
}

get_resource_data

Fetches data from a specific Redfish resource endpoint.

Parameters:
- url: The Redfish resource URL (e.g., https://192.168.1.100/redfish/v1/Systems/1)

Example usage:```
Get the system information from https://192.168.1.100/redfish/v1/Systems/1


**Response:**```json
{
  "headers": {
    "content-type": ["application/json"],
    "etag": ["\"12345\""]
  },
  "data": {
    "@odata.id": "/redfish/v1/Systems/1",
    "Name": "System1",
    "Manufacturer": "Example Corp"
  }
}

Configuration

The server supports configuration through environment variables or JSON files. Configuration is validated at startup to ensure proper setup.

Configuration Methods

  1. JSON File (Recommended for complex configurations):bash ./bin/redfish-mcp --config config.json

  2. Environment Variables (Default):bash export REDFISH_HOSTS='[{"address": "192.168.1.100"}]' ./bin/redfish-mcp

JSON Configuration File

Create a config.json file with the complete configuration:```json
{
"redfish": {
"hosts": [
{
"address": "192.168.1.100",
"port": 443,
"username": "admin",
"password": "secret123",
"auth_method": "session",
"tls_server_ca_cert": "/path/to/ca-cert.pem"
}
],
"port": 443,
"auth_method": "session",
"username": "default_user",
"password": "default_pass",
"tls_server_ca_cert": "",
"insecure_skip_verify": false,
"discovery_enabled": false,
"discovery_interval": 30
},
"mcp": {
"transport": "stdio",
"log_level": "INFO"
}
}


### Accessing Servers Without SSL Certificates

For development or testing with Redfish servers that have self-signed or invalid SSL certificates, you can skip certificate verification:

**Environment Variable:**```bash
export REDFISH_INSECURE_SKIP_VERIFY=true

JSON Configuration:```json
{
"redfish": {
"insecure_skip_verify": true
}
}


⚠️ **Security Warning:** Only use `insecure_skip_verify` in development or trusted environments. This option disables SSL certificate verification, making connections vulnerable to man-in-the-middle attacks.

### Environment Variables

| Variable | Description | Default | Required |
|----------|-------------|---------|----------|
| `REDFISH_CONFIG_FILE` | Path to JSON config file | - | No |
| `REDFISH_HOSTS` | JSON array of host configs | `[{"address":"127.0.0.1"}]` | Yes* |
| `REDFISH_PORT` | Default Redfish port | `443` | No |
| `REDFISH_AUTH_METHOD` | Auth method: `basic` or `session` | `session` | No |
| `REDFISH_USERNAME` | Default username | `""` | No |
| `REDFISH_PASSWORD` | Default password | `""` | No |
| `REDFISH_SERVER_CA_CERT` | CA certificate path | `""` | No |
| `REDFISH_INSECURE_SKIP_VERIFY` | Skip SSL certificate verification | `false` | No |
| `REDFISH_DISCOVERY_ENABLED` | Enable SSDP discovery | `false` | No |
| `REDFISH_DISCOVERY_INTERVAL` | Discovery interval (seconds) | `30` | No |
| `MCP_TRANSPORT` | Transport: `stdio`, `sse`, `streamable-http` | `stdio` | No |
| `MCP_REDFISH_LOG_LEVEL` | Log level: `DEBUG`, `INFO`, `WARNING`, `ERROR`, `CRITICAL` | `INFO` | No |

*Required when not using JSON config file

### Host Configuration

Each host in `REDFISH_HOSTS` or the JSON file can specify:

- `address` (required): IP or hostname
- `port` (optional): Port number
- `username` (optional): Host-specific username
- `password` (optional): Host-specific password
- `auth_method` (optional): `basic` or `session`
- `tls_server_ca_cert` (optional): Custom CA certificate path

### Validation

The server validates configuration on startup and exits with detailed error messages if invalid.

## Running the Server

### Basic Usage```bash
# Build the server
go build -o bin/redfish-mcp ./cmd/redfish-mcp

# Set configuration
export REDFISH_HOSTS='[{"address": "192.168.1.100", "username": "admin", "password": "secret"}]'

# Run with stdio transport (default)
./bin/redfish-mcp

# Or use a config file
./bin/redfish-mcp --config redfish-config.json

Transports

The server supports multiple MCP transport mechanisms:

stdio Transport (Default)

Standard input/output communication for direct integration with MCP clients.```bash
export MCP_TRANSPORT="stdio"
./bin/redfish-mcp


#### SSE Transport (Server-Sent Events)
Network-based communication over HTTP for remote clients.```bash
export MCP_TRANSPORT="sse"
./bin/redfish-mcp
# Server will be available at http://localhost:8000/sse

streamable-http Transport

Alternative HTTP-based transport for specific MCP implementations.```bash
export MCP_TRANSPORT="streamable-http"
./bin/redfish-mcp


### Makefile Targets

Use the provided Makefile for common operations:```bash
make go-build      # Build the binary
make go-run        # Run the server
make go-test       # Run tests
make go-fmt        # Format code
make go-vet        # Lint code

Integration with MCP Clients

Claude Desktop

Add the server to your claude_desktop_config.json:```json
{
"mcpServers": {
"redfish": {
"command": "/path/to/bin/redfish-mcp",
"env": {
"REDFISH_HOSTS": "[{\"address\": \"192.168.1.100\", \"username\": \"admin\", \"password\": \"secret123\"}]",
"MCP_TRANSPORT": "stdio"
}
}
}
}


### VS Code with GitHub Copilot

Configure in your VS Code settings or `.vscode/mcp.json`:```json
{
  "mcp": {
    "servers": {
      "redfish": {
        "command": "/path/to/bin/redfish-mcp",
        "env": {
          "REDFISH_HOSTS": "[{\"address\": \"192.168.1.100\", \"username\": \"admin\", \"password\": \"secret123\"}]",
          "MCP_TRANSPORT": "stdio"
        }
      }
    }
  }
}

MCP Inspector

Test the server with the MCP Inspector:```bash
npx @modelcontextprotocol/inspector /path/to/bin/redfish-mcp


For more information, see the VS Code documentation.

## Testing

### Unit Tests

Run the Go test suite:```bash
# Run all tests
go test ./...

# Run with race detection
go test -race ./...

# Run with coverage
go test -cover ./...

# Using Makefile
make go-test

MCP Inspector

Test the server interactively with the MCP Inspector:```bash

Build and test

go build -o bin/redfish-mcp ./cmd/redfish-mcp
npx @modelcontextprotocol/inspector ./bin/redfish-mcp


### Integration Testing

The server can be tested against real Redfish hardware or emulators. Ensure your `REDFISH_HOSTS` configuration points to accessible endpoints.

## Example Use Cases
- **AI Assistants**: Enable LLMs to fetch infrastructure data via Redfish API.
- **Chatbots & Virtual Agents**: Retrieve data, and personalize responses.

## Development

### Prerequisites

- Go 1.21 or later
- Git

### Setup```bash
# Clone the repository
git clone https://github.com/theoriginalaiexplorer/mcp-redfish-go.git
cd mcp-redfish-go

# Install dependencies
go mod tidy

# Build
go build ./cmd/redfish-mcp

Development Workflow```bash

Format code

go fmt ./...

Lint code

go vet ./...

Run tests

go test ./...

Build for development

go build -o bin/redfish-mcp ./cmd/redfish-mcp

Run the server

./bin/redfish-mcp


### Project Structure```
.
├── cmd/redfish-mcp/          # Main application
│   └── main.go              # Entry point
├── pkg/                     # Go packages
│   ├── config/              # Configuration management
│   │   ├── config.go        # Config structs and validation
│   │   ├── env.go           # Environment parsing
│   │   └── config_test.go   # Unit tests
│   ├── redfish/             # Redfish client and discovery
│   │   ├── client.go        # HTTP client with retry logic
│   │   ├── discovery.go     # SSDP discovery
│   │   └── types.go         # Type definitions
│   ├── mcp/                 # MCP server implementation
│   │   └── server.go        # MCP server setup and tools
│   └── common/              # Shared utilities
│       └── hosts.go         # Host management
├── .github/workflows/       # CI/CD workflows
│   └── release.yml          # Release automation
├── Makefile                 # Build and development tasks
└── README.md               # This file

Code Quality

  • Formatting: go fmt for consistent formatting
  • Linting: go vet for static analysis
  • Testing: Comprehensive unit tests with go test
  • Modules: Go modules for dependency management

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes with tests
  4. Run go test ./... and go vet ./...
  5. Submit a pull request

License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Acknowledgments

  • Model Context Protocol for the protocol specification
  • DMTF Redfish for the API standard
  • Go community for the excellent tooling and libraries

常见问题

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

在客户端按下面的安装命令接入:npx @modelcontextprotocol/inspector /path/to/bin/redfish-mcp。装完在客户端配置里引用同一个包或端点。

MCP E52ce37d 怎么在客户端里配置?

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

MCP E52ce37d 收费吗?

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

MCP E52ce37d 需要 API Key 吗?

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

MCP E52ce37d 能提供哪些能力?

资料显示能力标签包括 基础设施管理、JavaScript、Session认证。具体工具清单以官方文档为准。

MCP E52ce37d 需要什么运行环境?

运行时为 Node.js;属于远程端点,不需要在本地装运行时。

MCP E52ce37d 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为SSE · 服务端推送。

热门专题

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

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