| name | augur-api |
| description | Augur API integration via MCP. Covers service discovery, multi-site CRUD operations across Augur microservices, and credential resolution. Use when querying or modifying Augur data (contacts, transactions, inventory, etc.). |
Augur API
MCP server exposing Augur microservices through 7 generic tools.
Tools
| Tool | Purpose |
|---|
augur_discover | List services or endpoints for a service |
augur_sites | List configured sites with default flag |
augur_list | List records (GET collection) |
augur_get | Get single record by ID |
augur_create | Create record (POST) |
augur_update | Update record (PUT) |
augur_delete | Delete record (DELETE) |
All 5 data tools (augur_list, augur_get, augur_create, augur_update, augur_delete) accept an optional site parameter to target a specific site. Omit site to use the default.
Usage Pattern
Always start with discovery:
augur_sites(): see which sites are configured and which is defaultaugur_discover(): lists all available servicesaugur_discover(service="<name>"): lists endpoints for a specific service- Use data tools for CRUD, passing
site when targeting a non-default site
Do NOT hardcode service names or endpoints. Use augur_discover to find them at runtime.
Authentication
Credentials resolve automatically from .simpleapps/ directories.
Resolution order (first match wins):
- Env vars:
AUGUR_TOKEN + AUGUR_SITE_ID
- Explicit file:
AUGUR_CREDS_FILE env var pointing to a JSON file
- Project file:
<cwd>/.simpleapps/augur-api.json
- Global file:
~/.simpleapps/augur-api.json
Project and global files are merged (project takes precedence).
Single-site format
{
"siteId": "my-site",
"jwt": "my-token"
}
Multi-site format
{
"site-a": { "jwt": "token-a" },
"site-b": { "jwt": "token-b" }
}
API Reference
Documentation hub: https://augur-api.info/
Services include items, pricing, commerce, orders, customers, payments, shipping, open-search, and more. Use augur_discover at runtime rather than hardcoding service names.
When Auth Fails
If tools return authentication errors:
- Check for
.simpleapps/augur-api.json in the project directory or home directory
- Verify the file contains valid credentials (single-site or multi-site format)
- Fallback: set
AUGUR_TOKEN and AUGUR_SITE_ID env vars
When the MCP Server Is Unavailable
If augur_* tools are not present in the toolset (server not configured) or every call returns connection errors:
- Stop trying. Repeated calls will keep failing.
- Tell the user the Augur API MCP is unavailable and ask whether to (a) fix it, (b) skip the data check, or (c) use a different approach (e.g., reading data directly from the codebase, asking the user for the value)
- MUST NOT fabricate API responses or guess at data the API would have returned
There is no documented HTTP fallback. The MCP server holds the credential and routing logic. If the MCP is down, that path is closed for this session.
