SMM Data-pro MCP 使用文档 SMM Data-pro MCP User Guide

SMM Data-pro MCP 是上海有色网（SMM）面向 AI 客户端的标准化数据接入服务，提供中文、英文两个服务端点，各端点均支持两种传输协议，按客户端能力任选其一。 SMM Data-pro MCP is Shanghai Metals Market's standardized data access service for AI clients. It is served from two endpoints — Chinese and English — each supporting two transport protocols; pick whichever your client supports.

三步完成接入。 Three simple steps, end to end.

1. 获取 API KeyGet your API Key 向 SMM 客户经理或商务联系人申请 Data-pro MCP 服务的 API Key；尚无对接人时，可通过 metal.com / smm.cn 官网的联系渠道申请。 Request a Data-pro MCP API Key from your SMM account manager or business contact. If you don't have one yet, reach out via the contact channels on metal.com / smm.cn.
2. 复制对应配置Copy the matching configuration 在常用客户端配置中找到您的客户端，点击配置块右上角的「复制配置」按钮，按卡片说明粘贴到对应位置。协议与端点参数详见 Streamable HTTP（推荐）与 SSE（兼容旧版）。 Find your client in the Client Setup Guide, click the "Copy config" button in the top-right corner of the config block, and paste it where the card says. Protocol and endpoint details are in Streamable HTTP (recommended) and SSE (legacy).
3. 替换 Key 并重启客户端Replace the key and restart your client 将配置中的 your-api-key 替换为您的真实 API Key，保存后重启客户端。在客户端的 MCP 服务器/工具列表中看到 smm-datapro 即表示接入成功；随后可发一条测试提问验证数据链路，例如「查询 SMM 1# 电解铜最新均价」。 Replace your-api-key with your real API Key, save, and restart the client. When smm-datapro appears in your client's MCP server/tool list, you're connected. Then send a test question to verify the data link, e.g. "What is the latest SMM 1# copper cathode average price?"

适用客户端：Cursor、Claude Code 等任何支持 MCP Streamable HTTP 的客户端；Claude Desktop 多数版本需经 mcp-remote 桥接（见第五部分）。所有请求与响应均通过单一端点完成。 Supported clients: Cursor, Claude Code, and any client supporting MCP Streamable HTTP; most Claude Desktop versions connect via the mcp-remote bridge (see Part 05). All requests and responses go through a single endpoint.

客户端配置Client Configuration

{
  "mcpServers": {
    "smm-datapro": {
      "transport": "http",
      "url": "https://datapromcp.smm.cn/mcp",
      "headers": {
        "api_key": "your-api-key"
      }
    }
  }
}

{
  "mcpServers": {
    "smm-datapro": {
      "transport": "http",
      "url": "https://datapromcp.metal.com/mcp",
      "headers": {
        "api_key": "your-api-key"
      }
    }
  }
}

将 your-api-key 替换为您的真实 API Key。各客户端实际配置的字段名略有差异，请以第五部分对应客户端的写法为准。 Replace your-api-key with your real API Key. Field names vary slightly between clients — follow the exact syntax on your client's card in Part 05.

SSE（Server-Sent Events）是面向仅支持 SSE 传输的旧客户端的兼容方案。连接与消息分别使用两个端点；新接入建议优先使用 Streamable HTTP。 SSE (Server-Sent Events) is the compatibility option for older clients that only support SSE transport. Connection and messages use two separate endpoints; new integrations should prefer Streamable HTTP.

客户端配置Client Configuration

{
  "mcpServers": {
    "smm-datapro": {
      "transport": "sse",
      "url": "https://datapromcp.smm.cn/sse",
      "headers": {
        "api_key": "your-api-key"
      }
    }
  }
}

{
  "mcpServers": {
    "smm-datapro": {
      "transport": "sse",
      "url": "https://datapromcp.metal.com/sse",
      "headers": {
        "api_key": "your-api-key"
      }
    }
  }
}

将 your-api-key 替换为您的真实 API Key。各客户端实际配置的字段名略有差异，请以第五部分对应客户端的写法为准。 Replace your-api-key with your real API Key. Field names vary slightly between clients — follow the exact syntax on your client's card in Part 05.

以下按客户端类型分组，给出主流 AI 客户端的具体接入方法。所有客户端指向同一服务：端点 URL 与 api_key 请求头完全一致，仅配置文件的字段名因客户端而异——请使用对应卡片的写法，勿在客户端之间互抄字段。 The guides below are grouped by client type. Every client connects to the same service — identical endpoint URL and api_key header; only the config field names differ per client. Use the exact syntax on each card and do not copy field names across clients.

{
  "mcpServers": {
    "smm-datapro": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://datapromcp.smm.cn/mcp",
        "--header",
        "api_key:your-api-key"
      ]
    }
  }
}

{
  "mcpServers": {
    "smm-datapro": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://datapromcp.metal.com/mcp",
        "--header",
        "api_key:your-api-key"
      ]
    }
  }
}

{
  "mcpServers": {
    "smm-datapro": {
      "url": "https://datapromcp.smm.cn/mcp",
      "headers": {
        "api_key": "your-api-key"
      }
    }
  }
}

{
  "mcpServers": {
    "smm-datapro": {
      "url": "https://datapromcp.metal.com/mcp",
      "headers": {
        "api_key": "your-api-key"
      }
    }
  }
}

{
  "mcpServers": {
    "smm-datapro": {
      "url": "https://datapromcp.smm.cn/mcp",
      "headers": {
        "api_key": "your-api-key"
      }
    }
  }
}

{
  "mcpServers": {
    "smm-datapro": {
      "url": "https://datapromcp.metal.com/mcp",
      "headers": {
        "api_key": "your-api-key"
      }
    }
  }
}

claude mcp add --scope user --transport http smm-datapro \
  https://datapromcp.smm.cn/mcp \
  --header "api_key: your-api-key"

claude mcp add --scope user --transport http smm-datapro \
  https://datapromcp.metal.com/mcp \
  --header "api_key: your-api-key"

[mcp_servers.smm-datapro]
url = "https://datapromcp.smm.cn/mcp"
http_headers = { api_key = "your-api-key" }

[mcp_servers.smm-datapro]
url = "https://datapromcp.metal.com/mcp"
http_headers = { api_key = "your-api-key" }

本节图标均为本页示意图形，并非各客户端官方标识；配置格式依据各客户端公开文档整理（2026-07 核验），如客户端改版请以其最新官方文档为准。 Icons in this section are illustrative glyphs for this page only, not official client marks. Config formats follow each client's public documentation (verified 2026-07); if a client changes, defer to its latest official docs.

所有请求通过 HTTP 请求头完成认证与追踪，支持以下三个请求头： All requests are authenticated and traced via HTTP headers. The following three headers are supported: