JustOneAPI MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUSTONEAPI_DEBUG | No | Enable debug logging to stderr | false |
| JUSTONEAPI_RETRY | No | Number of retries after first attempt | 1 |
| JUSTONEAPI_TOKEN | Yes | Your JustOneAPI authentication token | |
| JUSTONEAPI_BASE_URL | No | API endpoint URL | https://api.justoneapi.com |
| JUSTONEAPI_TIMEOUT_MS | No | Request timeout in milliseconds | 20000 |
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 clearly distinct role: discovery, schema retrieval, invocation, account balance, usage analytics, platform listing, and catalog refresh. The two account-related tools are separated by balance vs. spending trends, and the sequential workflow tools explicitly reference each other.
All tool names follow a consistent verb_noun snake_case pattern: search_, get_, call_, list_, refresh_. There are no mixed naming conventions or vague verbs, making the set predictable and easy to navigate.
Seven tools is well-scoped for an API aggregation/catalog service. Each tool supports a necessary part of the workflow or administrative/maintenance need without redundant or filler tools.
The core workflow is fully covered: search for endpoints, retrieve their schema, call them, and check account balance/usage afterward. Platform listing and catalog refresh round out the surface with no obvious dead ends or missing lifecycle steps.