Skip to main content
Glama
martin-1103
by martin-1103

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
health_checkA

Check if the MCP server is running properly

get_project_contextB

Get project context including environments and folders. Validates MCP token and returns enriched project data.

list_environmentsC

List all environments for current project

get_environment_detailsC

Get detailed environment information including variables

create_environmentC

Create a new environment with variables

update_environment_variablesC

Update environment variables (add/update/remove variables)

set_default_environmentC

Set an environment as the default for the project

delete_environmentC

Delete an environment

list_foldersC

List all folders for current project with optional tree view

create_folderC

Create a new folder in the project

update_folderC

Update folder name, description, or parent

delete_folderC

Delete a folder and all its contents

get_folder_detailsC

Get detailed information about a specific folder

list_endpointsB

List all endpoints with optional filtering by folder

get_endpoint_detailsC

Get detailed endpoint configuration with folder information

create_endpointC

Create a new endpoint in a folder

update_endpointC

Update existing endpoint configuration

test_endpointC

Test a single endpoint with optional environment variables

execute_flowC

Execute a flow with sequential or parallel endpoint testing

create_flowA

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:

  • ❌ Empty steps array

  • ❌ Missing required step fields (id, name, method, url)

  • ❌ Invalid step references (must use {{step.output}})

  • ✅ Use {{input.var}} for flow inputs

  • ✅ Use {{step.output}} for chaining steps

  • ✅ Define outputs to pass data between steps

get_flow_detailsC

Get detailed information about a specific flow

list_flowsC

List flows in the current project

delete_flowC

Delete a flow

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/martin-1103/mcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server