ironxyz
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IRON_API_KEY | No | Iron.xyz API key for authentication | |
| IRON_BASE_URL | No | Custom base URL for API calls | |
| IRON_ENVIRONMENT | No | Iron.xyz environment to use | production |
| IRON_READ_ONLY_MODE | No | Restrict to GET requests only | false |
| IRON_LOCAL_SPEC_PATH | No | Local fallback spec file path | ./ironxyz-openapi-spec.yaml |
| IRON_OPENAPI_SPEC_URL | No | Custom OpenAPI spec URL |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-all-endpointsA | Get a comprehensive overview of all available API endpoints organized by category/tag. Use this to explore the API structure and find endpoints related to your goal. |
| get-api-specsA | Get detailed specifications for a specific API endpoint including parameters, request/response schemas, and examples. Should be used to get a deeper understanding of an API endpoint you will use for code generation or for real API invoking. In case you intend to use the invoke-api-endpoint MCP tool, ALWAYS use this before, so you understand the full context of an API. |
| invoke-api-endpointA | Make an actual API call to the Iron API. Use this ONLY after getting complete endpoint specifications with the get-api-specs MCP tool. This tool requires proper authentication and can be in read-only mode if configured. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| find-endpoint | Discover the right API endpoint for your goal. This prompt provides intelligent suggestions and guides you through the proper workflow: list-all-endpoints -> get-api-specs -> invoke-api-endpoint |
| test-endpoint | Get step-by-step guidance for testing a specific API endpoint. Provides parameter examples, common use cases, and testing strategies. |
| analyze-response | Analyze and understand API response data. Get insights about data structure, next steps, and related endpoints you might need. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool serves a unique purpose: list-all-endpoints for discovery, get-api-specs for detailed specs, and invoke-api-endpoint for actual API calls. No overlap in functionality.
All tool names follow the verb_noun pattern with snake_case: 'list-all-endpoints', 'get-api-specs', 'invoke-api-endpoint'. Consistent and predictable.
Three tools is minimal but covers the essential workflow of exploring and using an API. Falls just short of the ideal range (3-15) but is not too sparse for the purpose.
The set covers the core lifecycle: list all endpoints, get specs for one, then invoke. Minor gaps like search/filtering but no dead ends in the primary workflow.