Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_check | Check if the MCP server is running properly |
| get_project_context | Get project context including environments and folders. Validates MCP token and returns enriched project data. |
| list_environments | List all environments for current project |
| get_environment_details | Get detailed environment information including variables |
| create_environment | Create a new environment with variables |
| update_environment_variables | Update environment variables (add/update/remove variables) |
| set_default_environment | Set an environment as the default for the project |
| delete_environment | Delete an environment |
| list_folders | List all folders for current project with optional tree view |
| create_folder | Create a new folder in the project |
| update_folder | Update folder name, description, or parent |
| delete_folder | Delete a folder and all its contents |
| get_folder_details | Get detailed information about a specific folder |
| list_endpoints | List all endpoints with optional filtering by folder |
| get_endpoint_details | Get detailed endpoint configuration with folder information |
| create_endpoint | Create a new endpoint in a folder |
| update_endpoint | Update existing endpoint configuration |
| test_endpoint | Test a single endpoint with optional environment variables |
| execute_flow | Execute a flow with sequential or parallel endpoint testing |
| create_flow | Create a new flow in the project using Steps format for API automation Example format: { "name": "User Registration Flow", "description": "Complete user registration with email verification", "folderId": "fld_456", "flow_data": { "version": "1.0", "steps": [ { "id": "register_user", "name": "Register New User", "method": "POST", "url": "{{baseUrl}}/api/users/register", "headers": {"Content-Type": "application/json"}, "body": "{"name": "{{userName}}", "email": "{{userEmail}}", "password": "{{password}}"}", "outputs": {"userId": "response.body.id", "activationToken": "response.body.token"} }, { "id": "verify_email", "name": "Verify Email Address", "method": "POST", "url": "{{baseUrl}}/api/auth/verify", "headers": {"Content-Type": "application/json"}, "body": "{"token": "{{register_user.activationToken}}"}", "outputs": {"verificationStatus": "response.body.status"} } ], "config": {"delay": 1000, "retryCount": 2, "parallel": false} }, "flow_inputs": [ {"name": "baseUrl", "type": "string", "required": true, "description": "Base API URL"}, {"name": "userName", "type": "string", "required": true, "description": "User full name"}, {"name": "userEmail", "type": "email", "required": true, "description": "User email"}, {"name": "password", "type": "password", "required": true, "description": "User password"} ] } 2-step API Testing Example: { "name": "API Integration Test", "description": "Test user creation and retrieval", "flow_data": { "version": "1.0", "steps": [ { "id": "create_user", "name": "Create User", "method": "POST", "url": "https://api.example.com/users", "headers": {"Authorization": "Bearer {{apiKey}}"}, "body": "{"name": "Test User", "email": "test@example.com"}", "expectedStatus": 201, "outputs": {"newUserId": "response.body.id"} }, { "id": "get_user", "name": "Retrieve Created User", "method": "GET", "url": "https://api.example.com/users/{{create_user.newUserId}}", "headers": {"Authorization": "Bearer {{apiKey}}"}, "expectedStatus": 200, "outputs": {"userData": "response.body"} } ] } } Common mistakes:
|
| get_flow_details | Get detailed information about a specific flow |
| list_flows | List flows in the current project |
| delete_flow | Delete a flow |