Apitaco MCP Server
Official<div align="center">
# apitaco-mcp-server
**MCP server for [Apitaco](https://apitaco.com).** Query your balance, usage, and pricing from any MCP-compatible client.
[](./LICENSE)
[](https://github.com/myapitaco/apitaco-mcp-server)
</div>
---
## What it does
Exposes 3 MCP tools to Claude Desktop / Cursor / Claude Code / Cline:
- `apitaco_get_balance` — current account balance in USD
- `apitaco_get_usage` — token + cost stats for last N days
- `apitaco_list_models` — supported models with per-1M pricing
Ask Claude: _"How much do I have left on Apitaco?"_ → it calls the tool and answers.
## Install
```bash
npm install -g @apitaco/mcp-server
```
Or run from source:
```bash
git clone https://github.com/myapitaco/apitaco-mcp-server
cd apitaco-mcp-server
npm install
npm run build
```
## Configure
### Claude Desktop
Edit `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS)
or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):
```json
{
"mcpServers": {
"apitaco": {
"command": "npx",
"args": ["-y", "@apitaco/mcp-server"],
"env": {
"APITACO_API_KEY": "sk-..."
}
}
}
}
```
Restart Claude Desktop. The `apitaco_*` tools appear in the tool list.
### Cursor
In Cursor settings → **Features** → **MCP**, add:
```json
{
"mcpServers": {
"apitaco": {
"command": "npx",
"args": ["-y", "@apitaco/mcp-server"],
"env": { "APITACO_API_KEY": "sk-..." }
}
}
}
```
### Claude Code
```bash
claude mcp add apitaco npx -y @apitaco/mcp-server
# then set the env var in your shell
export APITACO_API_KEY=sk-...
```
## Usage
After configuring, just ask Claude in any MCP client:
> "Check my Apitaco balance."
> "How much have I spent on Apitaco in the last 30 days?"
> "Which Apitaco models are cheapest for output?"
## Environment variables
| Var | Default | Description |
|---|---|---|
| `APITACO_API_KEY` | required | Get one at [my.apitaco.com/register](https://my.apitaco.com/register) |
| `APITACO_BASE_URL` | `https://api.apitaco.com/v1` | Override for self-hosted / staging |
## Related
- [Apitaco Node SDK](https://github.com/myapitaco/apitaco-node)
- [Apitaco Python SDK](https://github.com/myapitaco/apitaco-python)
- [Awesome Claude Tools](https://github.com/myapitaco/awesome-claude-tools)
- [Model Context Protocol](https://modelcontextprotocol.io/)
## License
MIT.
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.