@lstpsche/apidog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIDOG_MODULES | No | JSON map of module names to IDs (e.g. {"api":123}) | |
| APIDOG_PROJECT_ID | No | Apidog project ID | |
| APIDOG_CONFIG_PATH | No | Explicit path to .apidog.json config file | |
| APIDOG_ACCESS_TOKEN | No | Apidog personal access token |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apidog_modulesA | List all configured Apidog projects and their modules with names and IDs |
| apidog_exportA | Export full OpenAPI spec for an Apidog module |
| apidog_listA | List and search endpoints in an Apidog module. Supports keyword search (scored by relevance), filters, and pagination. |
| apidog_getA | Get full details of a single endpoint including operation object and referenced schemas |
| apidog_foldersA | Analyze folder structure of an Apidog module — counts, tree, unfoldered endpoints |
| apidog_import_openapiA | Import an OpenAPI spec into an Apidog module. Auto-batches large specs to avoid payload limits. Accepts a file path or inline JSON. |
| apidog_wipeA | Wipe ALL endpoints in an Apidog module. Requires confirm=true as safety gate. Irreversible. |
| apidog_updateA | Update a single endpoint via targeted partial spec import. Does not affect other endpoints. |
| apidog_deleteA | Delete an endpoint from Apidog. Exports current spec, removes the target, reimports with deleteUnmatchedResources. |
| apidog_pipelineA | Run the proven 3-step pipeline: (1) wipe module, (2) create cases from structured data, (3) overlay enriched OpenAPI spec in batches. Accepts file paths or inline data. |
| apidog_create_casesA | Create one or more endpoint cases (usage examples). Pass a single-item or multi-item array. Internally builds a Postman collection and imports safely. Never overwrites endpoint definitions — only manages cases. |
| apidog_diffA | Compare current Apidog state against a provided OpenAPI spec. Reports added, removed, and changed endpoints with field-level diffs. |
| apidog_run_testA | Run Apidog tests via CLI. Provide scenarioId for a single scenario OR folderId for all scenarios in a folder. |
| apidog_list_schemasA | List all component schemas in an Apidog module with types, property counts, and referencing endpoints. |
| apidog_get_schemaA | Get full JSON Schema definition by name, plus list of endpoints that reference it. |
| apidog_update_schemaB | Create or update a component schema via targeted spec import. |
| apidog_delete_schemaA | Delete a component schema. Refuses if the schema is still referenced by endpoints. |
| apidog_analyzeA | Analyze an Apidog module. Use checks param to select: "coverage" (missing summaries, descriptions, tags, etc.) and/or "validate" (duplicate IDs, orphaned schemas, missing params, etc.). Defaults to both. |
| apidog_bulk_updateA | Batch update endpoints. Target by explicit endpoints array OR keyword filters. Supports: addTags, removeTags, setFolder, setStatus, setSummaryPrefix, summaryFindReplace. Set confirm=false to preview. |
| apidog_export_markdownB | Export module documentation as Markdown. Groups endpoints by folder or tag. Suitable for README or docs sites. |
| apidog_export_curlA | Export endpoints as ready-to-use curl command examples with placeholder values. |
| apidog_export_postmanA | Convert module to a Postman Collection v2.1 format with folder structure and placeholder values. |
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 22 tools
Each tool targets a distinct operation, whether it's a specific export format (OpenAPI vs curl vs Postman vs Markdown), a single endpoint vs bulk operation, or schema vs endpoint management. The descriptions clearly differentiate overlapping concepts like update vs bulk_update and delete vs wipe.
All tools share the 'apidog_' prefix, which provides strong consistency. However, the pattern is not strictly verb_noun: modules, folders, pipeline, and diff are noun-style names, while most others are verbs or verb_noun. This minor inconsistency keeps it from a perfect score.
22 tools is on the heavier side but appropriate for a feature-rich Apidog API management server covering endpoints, schemas, imports/exports, testing, analysis, and bulk operations. Each tool serves a clear purpose, so the count feels justified rather than bloated.
The surface covers most of the core Apidog workflows: endpoint CRUD, schema CRUD, multiple export formats, OpenAPI import, testing, diff/analyze, and bulk updates. Minor gaps include no direct endpoint creation tool (though import_openapi and pipeline handle it) and no tool for listing test scenarios/folders.