API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getC | Make a GET HTTP request |
| postC | Make a pOST HTTP request |
| putC | Make a PUT HTTP request |
| deleteC | Make a DELETE HTTP request |
| auth_loginC | Authenticate against an API, extract a JWT, and store it locally for reuse |
| list_userC | List stored users and tokens from a token store |
| clear_userC | Remove a specific user or clear the token store |
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
The HTTP methods (get, post, put, delete) are clearly distinct, but auth_login and clear_user/list_user overlap in user/token management, which could cause confusion. The descriptions help clarify, but there is some functional overlap in the authentication tools.
The HTTP methods use simple verbs (get, post, put, delete), while the user/token tools use verb_noun patterns (auth_login, clear_user, list_user). This mixed convention is readable but inconsistent, with no uniform pattern across all tools.
With 7 tools, the count is well-scoped for an API server covering core HTTP operations and basic authentication management. Each tool has a clear purpose, and the number is neither too sparse nor excessive for the domain.
The toolset covers essential HTTP methods (GET, POST, PUT, DELETE) and basic authentication lifecycle (login, list, clear), but lacks advanced features like token refresh or error handling. Minor gaps exist, but agents can work around them for most API interactions.