loading…
Search for a command to run...
loading…
Wraps the SJTU Zhiyuan No.1 API as a local MCP server, allowing direct use of SJTU models in Claude Code and Codex without custom integration scripts.
Wraps the SJTU Zhiyuan No.1 API as a local MCP server, allowing direct use of SJTU models in Claude Code and Codex without custom integration scripts.
English | 中文
Turn your SJTU Zhiyuan No.1 API key into something you can actually use in Claude Code and Codex.
SJTU MCP wraps the SJTU-hosted model API as a local MCP server, so you can call these models directly from your normal agent workflow instead of hand-writing integration scripts over and over again.
Have you already applied for an SJTU Zhiyuan No.1 API key, but still found it hard to actually use in practice?
This project exists to solve exactly that problem:
Claude Code or CodexClaude CodeCodexFor most users, the simplest path is:
git clone this repocd into the project directoryClaude Code or Codexgit clone https://github.com/EternalWavee/sjtu-mcp.git
cd sjtu-mcp
pip install -e .
After installation, your MCP client can start the server automatically when needed. In normal use, you do not need to manually run the server command every time.
Required:
SJTU_API_KEYOptional:
SJTU_API_BASE_URLSJTU_DEFAULT_TEXT_MODELSJTU_DEFAULT_REASONING_MODELSJTU_DEFAULT_VISION_MODELSJTU_REQUEST_TIMEOUTHow to use them:
env block of your MCP configurationUse this if you want sjtu available in all your Claude Code projects on this machine.
claude mcp add sjtu --scope user -- python -m sjtu_mcp.server
Then:
~/.claude.jsonsjtu entryenv section from examples/claude-project.mcp.jsonyour-api-key with your real keyVerify:
claude mcp list
Use this if you want to commit a shared config into the repo for teammates.
How to use it:
.mcp.jsonyour-api-key with your real keyWindows / macOS example:
{
"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"
}
}
}
}
Use this if you only want the server for the current project and do not want to commit the config.
claude mcp add sjtu --scope local -- python -m sjtu_mcp.server
Then add the same env values to the corresponding MCP config entry.
Use this if you want sjtu available in all your Codex projects on this machine.
codex mcp add sjtu -- python -m sjtu_mcp.server
Then:
~/.codex/config.tomlyour-api-key with your real keyVerify:
codex mcp list
If you already manage ~/.codex/config.toml directly, you can use this template:
[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_modelssjtu_textsjtu_visionsjtu_cheap_task请调用 sjtu_vision 分析图片里面的内容 .assets/test.png


deepseek-chatminimax or glm-5deepseek-reasonerqwen3vlqwen3coder/models and /chat/completions.Добавь это в claude_desktop_config.json и перезапусти Claude Desktop.
{
"mcpServers": {
"sjtu-mcp": {
"command": "npx",
"args": []
}
}
}