mcp-server-apidebug
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFIG_DIR | No | Optional config directory override; generally not needed. When not set, uses `PROJECT_PATH/.setting/{TOOL_PREFIX}`. | |
| TOOL_PREFIX | No | Tool name prefix; default tools are `default_api_debug`, `default_api_config`, etc. | default |
| PROJECT_PATH | No | Project directory; uses current directory when not set. | . |
| API_DEBUG_BASE_URL | No | API base URL; when configured, no need to set `baseUrl` via `api_config`. | |
| API_DEBUG_LOGIN_URL | No | Login API URL. | /api/login |
| API_DEBUG_LOGIN_BODY | No | Login request body, supports JSON string or plain string. | {"username":"","password":""} |
| API_DEBUG_LOGIN_METHOD | No | Login API method. | POST |
| API_DEBUG_ALLOWED_METHODS | No | Allowed HTTP methods, comma-separated. | GET,POST,PUT,DELETE,PATCH |
| API_DEBUG_LOGIN_DESCRIPTION | No | Login tool description. | |
| API_DEBUG_LOGIN_USER_HEADER | No | Header name for user ID (extracted from login response). | new-api-user |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| default_api_loginA | API login authentication tool that uses environment variables for login credentials. Automatically extracts token from response and updates Authorization headers. Example: Call with optional baseUrl parameter to override default base URL |
| default_api_debugA | API debugging tool for directly executing API requests with automatic content-type detection and flexible body format support. Examples: GET /api/users with query params, POST /api/login with JSON body {"username":"admin","password":"123456"}, PUT /api/users/123 with form data "name=John&email=john@example.com" |
| default_api_helpA | API help tool that provides detailed documentation and examples for all API debugging tools. Use this to understand how to use api_debug, api_login, api_config, and api_execute tools effectively |
| default_api_executeA | Execute API requests by index from configured API list. Examples: execute API at index 0, execute with overrides {"method":"POST","body":{"key":"value"}} |
| default_api_configB | API configuration management tool for managing API settings, endpoints, and configurations. Examples: get config, set baseUrl to "https://api.example.com", updateHeaders with {"Authorization":"Bearer token"}, search APIs by keyword, list all configured APIs |
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 5 tools
Tools have distinct purposes (config, debug, execute, help, login). However, 'debug' and 'execute' both involve executing API requests, differing only in input method, which could cause minor confusion. Descriptions help clarify the distinction.
All tools follow the consistent 'default_api_<action>' prefix pattern. The action words (config, debug, execute, help, login) are all clear and follow a predictable structure, enabling easy tool selection.
With 5 tools, the set is well-scoped for an API debugging server. Each tool addresses a core task (configuration, direct execution, index-based execution, authentication, and help). No tools are superfluous.
The tool set covers essential API debugging workflows: configuration, authentication, and execution (both direct and by index). Minor gaps exist, such as a tool for viewing execution history or batch operations, but core functionality is solid.