simpleapps-com-augur-mcp

# Augur MCP Server > **This package is retired.** This is its final release, and it gets no further updates. > Use the hosted Augur API MCP server instead: > > ```bash > claude mcp add --transport http augur-api https://augur-api.io/mcp \ > --header "Authorization: Bearer <your agr-int user JWT>" > ``` > > The hosted server needs no install or credentials file. It reaches every endpoint in the > current SDK, and the site comes from your token. Progress: simpleapps-com/augur-api#137. FastMCP server exposing Augur API microservices as 7 generic MCP tools. ## Install ```bash uvx simpleapps-com-augur-mcp ``` ## Authentication Credentials are resolved in this order (first match wins): 1. **Environment variables** — `AUGUR_TOKEN` + `AUGUR_SITE_ID` 2. **Explicit file** — `AUGUR_CREDS_FILE` env var pointing to a JSON file (supports `~`) 3. **Project file** — `.simpleapps/augur-api.json` in the current working directory 4. **Global file** — `~/.simpleapps/augur-api.json` Steps 3 and 4 are merged — project credentials take precedence when the same site_id appears in both files. ### Single-site credentials ```json { "siteId": "your-site-id", "jwt": "your-jwt-token" } ``` ### Multi-site credentials Configure multiple sites in a single file: ```json { "acme-corp": { "jwt": "acme-jwt" }, "other-site": { "jwt": "other-jwt" } } ``` The format is auto-detected: a top-level `siteId` key means single-site, otherwise each key is the site ID and its value contains the JWT. ### Project + global merge You can keep site-specific credentials in your project and shared credentials globally: ``` ~/.simpleapps/augur-api.json → {"siteId": "shared-site", "jwt": "..."} ./project/.simpleapps/augur-api.json → {"siteId": "project-site", "jwt": "..."} ``` Both are loaded and merged. If the same `siteId` exists in both, the project file wins. ## MCP Configuration Minimal — no env vars needed when using project or global credentials: ```json { "mcpServers": { …