Apitaco MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APITACO_API_KEY | Yes | Get one at https://my.apitaco.com/register | |
| APITACO_BASE_URL | No | Override for self-hosted / staging | https://api.apitaco.com/v1 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apitaco_get_balanceA | Get the current Apitaco account balance in USD. Use this when the user asks 'how much do I have left' or 'what's my balance'. |
| apitaco_get_usageA | Get Apitaco usage stats for the last N days (default 7). Returns total tokens and cost. |
| apitaco_list_modelsA | List models available on Apitaco with their per-million-token pricing. |
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 3 tools
Each tool targets a distinct resource and action: balance, usage stats, and available models. There is no overlap in purpose, and an agent can easily select the correct tool based on the user's request.
All tools follow a consistent pattern: apitaco_ prefix plus a clear verb_noun structure (get_balance, get_usage, list_models). The convention is predictable and readable.
Three tools is appropriate for a focused account-information server. Each tool earns its place by covering a distinct read-only query without unnecessary surface area.
The surface covers the core account queries: balance, usage, and model pricing. Minor gaps like detailed historical usage breakdowns or account settings exist, but agents can work around them for the stated purpose.