RAP2 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAP2_SID | No | Logged-in Cookie SID (koa.sid value) | |
| RAP2_EMAIL | No | Login email (used with password authentication) | |
| RAP2_SID_SIG | No | Logged-in Cookie signature (koa.sid.sig value) | |
| RAP2_BASE_URL | No | RAP2 instance address | |
| RAP2_PASSWORD | No | Login password (used with email authentication) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rap2_test_connectionA | 测试连接并校验会话：探测 /repository/joined，必要时自动登录后再探测（可用提示："测试rap连接"、"确保已登录"） |
| rap2_ensure_sessionB | 使用环境参数登录并保存 Cookie 到会话缓存 |
| rap2_debug_login_infoB | 调试当前登录环境配置（不返回明文密码） |
| rap2_get_interface_by_idC | 根据接口 ID 获取接口详情 |
| rap2_get_repository_interfacesC | 获取仓库下的全部接口列表 |
| rap2_search_interfaces_by_keywordC | 按关键字搜索接口（可选限定仓库） |
| rap2_search_interfaces_by_pathC | 按请求路径搜索接口（可选限定仓库） |
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 7 tools
Each tool has a clearly distinct purpose with no ambiguity. The tools cover different aspects of RAP2 API interaction: login/session management (debug_login_info, ensure_session, test_connection), interface retrieval by different criteria (by_id, repository_interfaces, search_by_keyword, search_by_path), and connection testing. No overlap exists between these functions.
All tools follow a consistent 'rap2_' prefix with snake_case naming and clear verb_noun patterns (e.g., 'get_interface_by_id', 'search_interfaces_by_keyword'). The naming convention is uniform throughout the toolset, making it predictable and easy to understand.
With 7 tools, this server is well-scoped for its purpose of interacting with RAP2 API. The count is appropriate, covering essential operations like authentication, interface retrieval, and search functionalities without being overwhelming or too sparse. Each tool earns its place in the workflow.
The toolset provides good coverage for core RAP2 API operations, including login/session management and interface retrieval/search. However, there are minor gaps in CRUD operations for interfaces (e.g., no create, update, or delete tools) and repository management, which agents might need to work around for full lifecycle coverage.