MCP REST Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_REST_TOKEN | No | API token (required for token auth) | |
| MCP_REST_RETRIES | No | Number of retries for failed requests (default: 3) | 3 |
| MCP_REST_TIMEOUT | No | Request timeout in milliseconds (default: 30000) | 30000 |
| MCP_REST_BASE_URL | No | Base URL for the REST API (required) | |
| MCP_REST_PASSWORD | No | Password (required for login auth) | |
| MCP_REST_USERNAME | No | Username (required for login auth) | |
| MCP_REST_AUTH_TYPE | No | Authentication type: 'token' or 'login' (required) | |
| MCP_REST_CONFIG_FILE | No | Path to JSON configuration file | |
| MCP_REST_SWAGGER_URL | No | URL to Swagger/OpenAPI documentation | |
| MCP_REST_TOKEN_FIELD | No | Token field name in login response (default: access_token) | access_token |
| MCP_REST_LOGIN_ENDPOINT | No | Login endpoint path (required for login auth) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| configure_rest_clientC | Configure the REST client with base URL, authentication, and optional Swagger documentation URL |
| http_requestB | Make an HTTP request to the configured API |
| get_swagger_documentationA | Get the complete Swagger/OpenAPI documentation for available endpoints |
| search_endpointsB | Search for endpoints in the Swagger documentation |
| get_endpoint_infoC | Get detailed information about a specific endpoint |
| check_authenticationB | Check if the client is currently authenticated |
| logoutA | Logout and clear authentication state |
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 7 tools
Each tool has a distinct purpose: authentication checking, configuration, endpoint info, documentation retrieval, HTTP requests, logout, and endpoint search. No overlap.
All tool names follow the verb_noun snake_case pattern (e.g., check_authentication, get_endpoint_info), ensuring predictability.
7 tools cover the core functionality of a REST client server without being excessive or sparse, aligning well with the server's scope.
The tool set covers authentication lifecycle, API documentation exploration, and HTTP requests. Missing features like configuration management (e.g., updating base URL without reconfiguring) are minor.