Skip to main content
Glama

SJTU MCP

English | 中文

Claude Code Codex SJTU API Version License

将您的上海交通大学致远一号 API Key 转化为可以在 Claude Code 和 Codex 中实际使用的工具。

SJTU MCP 将上海交大托管的模型 API 封装为本地 MCP 服务器,因此您可以直接从常规的 Agent 工作流中调用这些模型,而无需反复手写集成脚本。

为什么需要这个项目

您是否已经申请了上海交通大学致远一号 API Key,但发现实际上手使用并不方便?

本项目正是为了解决这个问题:

  • 您已经拥有 API 访问权限

  • 您希望在 Claude Code 或 Codex 中使用它

  • 但上海交大的端点无法直接开箱即用地接入这些 Agent 工具

  • 您不想每次都重写集成层

Related MCP server: Claude-LMStudio-Bridge

特性亮点

  • 支持 Claude Code

  • 支持 Codex

  • 同时支持文本和视觉任务

  • 使用上海交大兼容 OpenAI 的端点

  • 自然融入现有的 MCP 工作流

目录

快速开始

对于大多数用户,最简单的路径是:

  1. git clone 本仓库

  2. cd 进入项目目录

  3. 执行一次安装

  4. 在 Claude Code 或 Codex 中将其添加为全局 MCP 服务器

git clone https://github.com/EternalWavee/sjtu-mcp.git
cd sjtu-mcp
pip install -e .

安装完成后,您的 MCP 客户端可以在需要时自动启动服务器。在正常使用中,您无需每次都手动运行服务器命令。

环境变量

必需:

  • SJTU_API_KEY

可选:

  • SJTU_API_BASE_URL

  • SJTU_DEFAULT_TEXT_MODEL

  • SJTU_DEFAULT_REASONING_MODEL

  • SJTU_DEFAULT_VISION_MODEL

  • SJTU_REQUEST_TIMEOUT

如何使用:

  • .env.example 仅作为模板,展示了您需要的变量

  • 在实际使用中,请将这些值放入 MCP 配置的 env 块中

Claude Code

推荐:用户范围

如果您希望在当前机器的所有 Claude Code 项目中使用 sjtu,请使用此方法。

claude mcp add sjtu --scope user -- python -m sjtu_mcp.server

然后:

  1. 打开 ~/.claude.json

  2. 找到 sjtu 条目

  3. 从 examples/claude-project.mcp.json 复制 env 部分

  4. 将 your-api-key 替换为您真实的 Key

验证:

claude mcp list

项目范围

如果您希望将共享配置提交到仓库中供团队成员使用,请使用此方法。

如何使用:

  1. 将 examples/claude-project.mcp.json 复制到项目根目录并命名为 .mcp.json

  2. 将 your-api-key 替换为您真实的 Key

  3. 根据需要调整默认模型和超时时间

Windows / macOS 示例:

{
  "mcpServers": {
    "sjtu": {
      "command": "python",
      "args": ["-m", "sjtu_mcp.server"],
      "env": {
        "SJTU_API_BASE_URL": "https://models.sjtu.edu.cn/api/v1",
        "SJTU_API_KEY": "your-api-key",
        "SJTU_DEFAULT_TEXT_MODEL": "deepseek-chat",
        "SJTU_DEFAULT_REASONING_MODEL": "deepseek-reasoner",
        "SJTU_DEFAULT_VISION_MODEL": "qwen3vl",
        "SJTU_REQUEST_TIMEOUT": "180"
      }
    }
  }
}

本地范围

如果您只想在当前项目中使用该服务器,且不想提交配置,请使用此方法。

claude mcp add sjtu --scope local -- python -m sjtu_mcp.server

然后将相同的 env 值添加到相应的 MCP 配置条目中。

Codex

推荐:全局设置

如果您希望在当前机器的所有 Codex 项目中使用 sjtu,请使用此方法。

codex mcp add sjtu -- python -m sjtu_mcp.server

然后:

  1. 打开您的 ~/.codex/config.toml

  2. 从 examples/codex-config.toml 复制内容

  3. 将 your-api-key 替换为您真实的 Key

  4. 保存并重新加载 Codex 或重新加载 MCP

验证:

codex mcp list

配置文件设置

如果您已经直接管理 ~/.codex/config.toml,可以使用此模板:

[mcp_servers.sjtu]
command = "python"
args = ["-m", "sjtu_mcp.server"]

[mcp_servers.sjtu.env]
SJTU_API_BASE_URL = "https://models.sjtu.edu.cn/api/v1"
SJTU_API_KEY = "your-api-key"
SJTU_DEFAULT_TEXT_MODEL = "deepseek-chat"
SJTU_DEFAULT_REASONING_MODEL = "deepseek-reasoner"
SJTU_DEFAULT_VISION_MODEL = "qwen3vl"
SJTU_REQUEST_TIMEOUT = "180"

工具

  • sjtu_models

  • sjtu_text

  • sjtu_vision

  • sjtu_cheap_task

示例

输入

请调用 sjtu_vision 分析图片里面的内容 .assets/test.png

test

输出

answer

模型使用建议

  • deepseek-chat

    • 适用于摘要、重写、清理和低风险文本任务的默认模型

  • minimax 或 glm-5

    • 适用于轻量级重写、分类或提取任务

  • deepseek-reasoner

    • 适用于真正需要多步推理的任务

  • qwen3vl

    • 适用于截图、OCR 风格提取和图像理解的强大起点

  • qwen3coder

    • 适用于代码相关的实用任务

注意事项

  • 本服务器目前假设上海交大端点支持兼容 OpenAI 的 /models 和 /chat/completions 接口。

  • 本地图像在发送前会被编码为数据 URL。

  • 如果您的校园端点有特定于模型的怪癖,请在 src/sjtu_mcp/server.py 中扩展路由。

Available Tools

4 tools
sjtu_cheap_taskC

Route common low-risk jobs like summarize, rewrite, classify, and extract.

Inputs: task (required), content (required), image_path, image_url, +1 more. Returns: result

sjtu_modelsA

List available models from the SJTU endpoint.

Inputs: no named parameters. Returns: result

sjtu_textC

Run a plain text task against the SJTU OpenAI-compatible API.

Inputs: prompt (required), model, system_prompt, temperature, +1 more. Returns: result

sjtu_visionC

Run an image understanding task against the default vision model.

Inputs: prompt (required), image_path, image_url, model, +3 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation3/5

    sjtu_cheap_task and sjtu_text both handle text tasks, creating potential confusion. sjtu_cheap_task specifies common low-risk jobs, but the boundary with sjtu_text is unclear. sjtu_models and sjtu_vision are distinct.

    Naming Consistency4/5

    All tools share the consistent 'sjtu_' prefix and snake_case naming, but the pattern varies between adjective_noun (sjtu_cheap_task) and noun-only (sjtu_models, sjtu_text, sjtu_vision), which is mostly consistent with minor deviations.

    Tool Count5/5

    Four tools is well-scoped for the SJTU endpoint, covering essential capabilities (listing models, text, vision, and a cheap task option) without unnecessary bloat.

    Completeness4/5

    The set covers core functionalities, but the overlap between sjtu_cheap_task and sjtu_text suggests redundancy; missing streaming or embeddings are minor gaps for basic use.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers