Account Settings
→ API Access Token
<access-token>
in the configuration below<project-id>
in the configuration belowmcp.json
. Remember to replace <access-token>
and <project-id>
with your own:{
"mcpServers": {
"API specification": {
"command": "npx",
"args": [
"-y",
"apidog-mcp-server@latest",
"--project=<project-id>"
],
"env": {
"APIDOG_ACCESS_TOKEN": "<access-token>"
}
}
}
}
Please fetch API specification via MCP and tell me how many endpoints exist in the project
<access-token>
and <project-id>
with your personal Apidog API access token and project ID.<project-id>
. For clarity, name each MCP Server following the format "xxx API Specification"."APIDOG_ACCESS_TOKEN": "<access-token>"
and instead, configure the APIDOG_ACCESS_TOKEN
as an environment variable on each member's machine to prevent token leakage.<API address of the on-premise server, starting with http:// or https://>
". Additionally, ensure network access to www.npmjs.com
properly.{
"mcpServers": {
"API specification": {
"command": "npx",
"args": [
"-y",
"apidog-mcp-server@latest",
"--project=<project-id>",
// Required for on-premise deployment:
"--apidog-api-base-url=<API address of the on-premise server, starting with http:// or https://>"
],
"env": {
"APIDOG_ACCESS_TOKEN": "<access-token>"
}
}
}
}