Connect an MCP client
Point your MCP client at the stateless Streamable HTTP endpoint. The mcpServers form shown here is what Cursor, VS Code and many other clients use; some clients spell the key servers and accept the transport implicitly, so check your client's schema:
{
"mcpServers": {
"wheatomics": {
"type": "http",
"url": "https://wheatomics.sdau.edu.cn/api/mcp"
}
}
}
Claude Code can register the same server from a shell:
claude mcp add --transport http wheatomics https://wheatomics.sdau.edu.cn/api/mcp
Check connectivity with an MCP initialize JSON-RPC call; the Accept header must allow both a JSON response and an event stream:
curl -sS -X POST https://wheatomics.sdau.edu.cn/api/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize",
"params":{"protocolVersion":"2025-06-18","capabilities":{},
"clientInfo":{"name":"curl","version":"1.0"}}}'
Legacy SSE (single-worker / local development only). The original transport is still registered at GET /api/mcp/sse (messages: POST /api/mcp/messages). Use the same client config with "type": "sse" and "url": "https://wheatomics.sdau.edu.cn/api/mcp/sse", or register it with Claude Code:
claude mcp add --transport sse wheatomics https://wheatomics.sdau.edu.cn/api/mcp/sse
Production runs multiple workers that cannot pin an SSE session, so use Streamable HTTP there. Your client must support remote Streamable HTTP MCP servers (or the legacy SSE transport); local stdio-only clients cannot connect to these endpoints directly.