// MCP TOOL REFERENCE

APIDOG TESTS TOOLS

30 tools from the Apidog Tests MCP Server, categorised by risk level.

// ALL 30 APIDOG TESTS TOOLS

READ 14 tools

Read get_endpoint_statistics Get endpoint test coverage statistics Read get_test_case Get full details of a single test case by its ID, including parameters, request body, and assertions Read get_test_data Get a specific test data record including the CSV data rows and column definitions. Read get_test_scenario_steps Get the steps (API calls) for a test scenario. Each step contains the full httpApiCase with parameters, aut... Read get_test_suite Get full details of a test suite, including its items (test cases and scenarios). Read list_api_endpoints List API endpoints tree with IDs, names, and folder structure. Use this to find apiDetailId values needed f... Read list_environments List all environments (DEV, TEST, PROD, etc.) with their base URLs Read list_runners List available test runners (self-hosted agents for running tests) Read list_test_case_categories List test case categories (e.g. Positive, Negative, Edge Case) Read list_test_case_tags List available test case tags for categorizing test cases Read list_test_cases List test cases (id, name, type, apiDetailId, categoryId, tagIds). Supports filtering by endpoint and pagin... Read list_test_data List test data records for a test case. Returns metadata (id, environmentId, relatedId) but not the actual ... Read list_test_scenarios List all test scenarios (compact summary: id, name, folderId, priority, tags, description, ordering, status... Read list_test_suites List all test suites (compact summary: id, name, folderId, priority, tags, description, ordering, status). ...

WRITE 11 tools

Write create_scenario_folder Create a folder for organizing test scenarios. Folders can be nested via parentId. Write create_suite_folder Create a folder for organizing test suites. Folders can be nested via parentId. Write create_test_case Create a test case for an API endpoint. Requires apiDetailId (from list_api_endpoints) and responseId. Use ... Write create_test_cases_bulk Create multiple test cases at once. Each item follows the same schema as create_test_case. Write create_test_data Create a test data record for a test case. The data field is CSV-formatted: first line is the column header... Write create_test_scenario Create a new test scenario (multi-step test flow). Use list_test_scenarios first to find valid folderIds an... Write create_test_suite Create a new test suite for CI grouping. Suites can contain test cases and test scenarios. Write update_test_case Update an existing test case. Pass only the fields you want to change. The tool fetches the current state f... Write update_test_data Update an existing test data record. Fetches current state first and merges changes. Write update_test_scenario_steps Set or update the steps in a test scenario. Each step references an API endpoint via bindId (apiDetailId). ... Write update_test_suite_items Replace items in a test suite. Each item is a group with a UUID, a type, and a nested array of references. ...

DESTRUCTIVE 5 tools

Destructive delete_scenario_folder Delete a test scenario folder by ID. The folder must be empty. This cannot be undone. Destructive delete_test_case Delete a test case by ID. This cannot be undone. Destructive delete_test_data Delete a test data record by ID. Destructive delete_test_scenario Delete a test scenario by ID. This cannot be undone. Destructive delete_test_suite Delete a test suite by ID. This cannot be undone.

// RUNNING THIS SERVER

The managed route: connect Apidog Tests through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y @acabala/apidog-tests-mcp

// FAQ

How many tools does the Apidog Tests MCP server have? +

The Apidog Tests MCP server exposes 30 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Apidog Tests tools? +

Route the Apidog Tests server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Apidog Tests tools fall into? +

Apidog Tests tools are categorised as Read (14), Write (11), Destructive (5). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.