COPT-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RERANKER_URL | Yes | Reranker API endpoint URL (e.g., https://api.siliconflow.cn/v1/rerank) | |
| EMBEDDING_URL | Yes | Embedding model API endpoint URL (e.g., https://api.siliconflow.cn/v1/embeddings) | |
| RERANKER_API_KEY | Yes | API key for the reranker service | |
| EMBEDDING_API_KEY | Yes | API key for the embedding service |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_citationA | 获取COPT的引用格式 Args: citation_type: 引用类型，包括： - "word": 适用于word文档 - "bibtex": 适用于bibtex文件 |
| get_referenceA | 获取COPT的指定语言接口对应问题的参考示例,推荐在调用COPT解决对应问题前调用 Args: problem_type: 求解问题类型，目前支持的问题类型如下： - "LP": 线性规划(LP) - "MIP": 混合整数规划(MIP) - "SOCP": 二阶锥规划(SOCP) - "NLP": 非线性规划(NLP) language: API接口语言，目前支持的语言如下： - "Python": Python接口 |
| get_api_docA | 根据查询指令召回并排序最相似的API文档,在你不清楚COPT的相关API用法时,可以调用此工具 Args: instructions: 查询指令,支持自然语言描述与代码片段的查询,参考的查询指令如下： - "name": 查询API名称,如"Model.addConstr()"/"Envr()" - "description": 查询需求描述,如"使用矩阵建模添加一组线性约束" language: API接口语言,目前支持的语言如下： - "Python": Python接口 domain: 查询指令对应的字段,目前支持的领域如下： - "name": 查询API名称 - "description": 查询API描述 recall_num: 查询召回数量,默认为10,最大为25 return_num: 重排序后最终返回数量,默认为3,最大为8 Hints: - 在能够明确API名称时，优先选择"name"字段 - 在希望精准查询特定API时，推荐选择"name"字段 - 在希望根据需求描述模糊查询时，推荐选择"description"字段 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct resource: formatting citations, fetching reference examples, and searching API docs. There is no overlap in their purposes, and the descriptions make the appropriate use case for each clear.
All tool names follow a consistent 'get_' prefix followed by a noun (citation, reference, api_doc). The naming pattern is uniform and predictable, making it easy to infer functionality.
With 3 tools covering citations, examples, and API documentation, the server is well-scoped for its purpose as a COPT reference helper. The small count is appropriate because each tool provides distinct, essential functionality.
The server covers the main reference needs: getting citations, example code for specific problem types, and API documentation search. Minor gaps exist (e.g., only Python language support, no tool to list all available options), but these are acceptable for the stated domain.