Any-API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_BASE | Yes | The base URL of the API | |
| AUTH_MODE | No | Authentication mode: none, bearer, header, basic, or query | none |
| AUTH_TOKEN | No | Bearer token or header value depending on auth mode | |
| AUTH_HEADER | No | Header name used if AUTH_MODE=header | Authorization |
| AUTH_QUERY_KEY | No | Query parameter key used if AUTH_MODE=query | api_key |
| ALLOW_DESTRUCTIVE | No | Guard writes - set to true to allow POST/PUT/DELETE operations | false |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| api_probeC | Probe an API path with any method (safe). |
| api_getB | Generic GET against API_BASE (safe). |
| api_postC | Generic POST against API_BASE (guarded). |
| api_putC | Generic PUT against API_BASE (guarded). |
| api_deleteC | Generic DELETE against API_BASE (guarded). |
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 5 tools
The five tools map cleanly to distinct HTTP operations (probe, GET, POST, PUT, DELETE), so an agent can generally tell them apart. The only mild overlap is api_probe with any method potentially covering the same requests as the specific verb tools, but its 'safe probe' intent separates it clearly enough.
All tools follow a consistent api_<verb> pattern, with lowercase snake_case throughout. The verbs are standard HTTP operations, making the naming predictable and easy to infer.
Five tools is well-scoped for a generic API interaction server. Each tool covers a necessary HTTP operation without redundancy or bloat.
The common HTTP methods are covered, along with a safe probing option, which handles most API interaction needs. The surface has a minor gap: PATCH is missing, and the descriptions don't explicitly show how custom paths, headers, or bodies are specified.