rest_api_mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`API_OTP`	No	The OTP code to submit to API_VERIFY_ENDPOINT. On staging this is typically a fixed test code.
`API_EMAIL`	No	Login email (required for authenticated endpoints)
`API_PASSWORD`	No	Login password (required for authenticated endpoints)
`REST_BASE_URL`	Yes	Base API URL, no trailing slash
`API_TOKEN_PATH`	No	Dot-path to token in login/verify response, e.g. data.access_token
`API_SWAGGER_URL`	No	OpenAPI JSON URL for fetch_spec, search_endpoints, and login auto-discovery
`API_LOGIN_ENDPOINT`	No	Override login path, e.g. /auth/sign-in
`API_VERIFY_ENDPOINT`	No	Path of the 2FA/OTP verify step. Setting this enables two-step auth. Example: /auth/verify-otp
`API_LOGIN_CREDENTIALS`	No	JSON object of extra fields merged into the login POST body alongside email/password. Use for role, source, tenantId, etc. Example: {"role":"admin"}
`API_VERIFY_CREDENTIALS`	No	JSON object of extra fields merged into the verify POST body, beyond the auto-carried session identifiers and OTP. Example: {"client_id":"web-app"}
`REST_ENABLE_SSL_VERIFY`	No	Set false to skip TLS cert validation (dev/staging only)	true
`REST_RESPONSE_SIZE_LIMIT`	No	Max response characters before truncation	100000

Features and capabilities supported by this server

Capability	Details
`tools`	{}
`resources`	{}

Functions exposed to the LLM to take actions

Name	Description
fetch_specA	Fetches the OpenAPI/Swagger JSON spec for this API. Use this to discover endpoint paths, HTTP methods, and request body schemas before calling request().
search_endpointsA	Fuzzy-search the API spec by keyword. Use this when you don't know the exact path. Searches across path, HTTP method, summary, description, tags, and operationId. Returns matching endpoints with their method, full path, summary, and required parameters.
requestA	Makes an authenticated API call. Handles login automatically — if the token is expired it re-logins transparently. Returns the full response body plus login_data (which contains IDs like pharmacyId returned from login).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
`Implementation Workflow Guide`	Step-by-step guide for implementing a REST API endpoint in Flutter using this MCP server

Latest Blog Posts

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Muhammed-AbdelGhany/rest_api_mcp'

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