JustOneAPI MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUSTONEAPI_TOKEN | No | Your JustOneAPI API token, used for local stdio connections. Not required for remote HTTP connections using OAuth. |
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 |
|---|---|
| search_endpointsA | Find JustOneAPI endpoint candidates from natural language. Returns endpoint_id candidates; call get_endpoint_schema next. |
| get_endpoint_schemaA | Get the full schema and parameter contract for an endpoint_id returned by search_endpoints. |
| call_endpointA | Validate params and make one JustOneAPI endpoint call by endpoint_id. The call may incur charges under the bound API Token's current pricing and budget. Params should use snake_case names from get_endpoint_schema. |
| get_account_balanceA | Get the current JustOneAPI token's available balance and currency. Use this when the user asks about account balance, remaining balance, or whether the token can continue calling APIs. |
| get_usage_summaryA | Get the current JustOneAPI token's API usage and spending summary, including recent call trends and spending trends. |
| list_platformsA | List supported JustOneAPI platforms and endpoint counts. |
| refresh_catalogA | Admin-only. Refresh the endpoint catalog from JustOneAPI OpenAPI documents. |
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 role in the endpoint discovery, schema retrieval, and invocation workflow; search_endpoints, get_endpoint_schema, and call_endpoint are clearly sequential and non-overlapping. The financial tools get_account_balance and get_usage_summary address different concerns (current balance vs. usage/spending trends), and list_platforms/refresh_catalog are distinct administrative actions.
All seven tools follow a consistent snake_case, verb-first pattern (search_, get_, call_, list_, refresh_), with clear object or action names. The convention is uniform throughout, making the tool set predictable and easy to scan.
Seven tools are well-scoped for an API gateway and catalog server, covering discovery, schema inspection, invocation, account management, platform listing, and admin refresh. There is no redundancy; each tool earns its place.
The surface covers the full lifecycle for interacting with JustOneAPI: finding endpoints, retrieving their schemas, making validated calls, checking account balance and usage, listing supported platforms, and refreshing the catalog. No obvious gaps remain for the stated purpose.