ApiPost MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIPOST_HOST | No | API service address | https://open.apipost.net |
| APIPOST_TOKEN | Yes | API access token (format: apk_xxxxxxxxx) | |
| APIPOST_SECURITY_MODE | No | Security mode (safe/full) | safe |
| APIPOST_DEFAULT_TEAM_NAME | No | Default team name | |
| APIPOST_DEFAULT_PROJECT_NAME | No | Default project name |
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 |
|---|---|
| apipost_test_connectionB | 测试ApiPost MCP连接状态和配置信息，验证服务可用性 |
| apipost_workspaceC | 工作空间管理：查看当前工作空间、列出团队和项目、切换工作空间 |
| apipost_create_folderC | 创建API文档目录，支持在指定父目录下创建新的文件夹 |
| apipost_smart_createB | API接口文档生成器（字段列表驱动）。规则：responses 只传 fields，不传 data；headers/query/body/cookies 统一用字段列表，嵌套用 .，数组用 []；example 填真实值（不要 JSON 字符串）；所有字段含父级都必须写 desc，父级需显式声明。例如：{"key":"data","desc":"返回体","type":"object"},{"key":"data.user","desc":"用户","type":"object"},{"key":"data.user.id","desc":"用户ID","type":"integer","example":1} |
| apipost_listC | 查看项目API列表，支持强化的目录层级搜索和父子关系定位 |
| apipost_updateC | 修改API接口文档。规则同创建：responses 只用 fields（必填），不要传 data；headers/query/body/cookies 统一用字段列表，嵌套用 .，数组用 []，example 填真实值；所有字段含父级必须写 desc，父级需显式声明。例如：{"key":"data","desc":"返回体","type":"object"},{"key":"data.user","desc":"用户","type":"object"},{"key":"data.user.id","desc":"用户ID","type":"integer","example":1} |
| apipost_detailC | 查看API接口的详细配置信息，包括完整的请求参数、响应格式、认证设置等。 |
| apipost_deleteA | 批量删除API接口文档，支持单个或多个接口删除。删除前先用apipost_list查看接口列表获取ID |
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 8 tools
Each tool has a clearly distinct purpose with no overlap: folder creation, deletion, detail viewing, listing, smart creation, connection testing, updating, and workspace management. The descriptions clearly differentiate their functions, making misselection unlikely.
All tools follow a consistent 'apipost_verb_noun' pattern with snake_case throughout (e.g., apipost_create_folder, apipost_detail, apipost_test_connection). This predictability makes the tool set easy to navigate and understand.
With 8 tools, this server is well-scoped for API documentation management. Each tool earns its place by covering essential operations like CRUD for API docs, workspace handling, and connection testing, without being overly sparse or bloated.
The tool set provides strong coverage for API documentation management, including create, read, update, delete, list, and workspace operations. A minor gap is the lack of a tool for moving or copying API docs between folders, but agents can work around this using existing tools.