Developer Documentation

MCP server

Use Augure from the AI tools you already work in. A compatible assistant connects to Augure's remote MCP server and can call Augure models as a tool, billed to your Augure developer account at the same rates as the API.

Endpoint: https://mcp.augureai.ca/mcp

What this enables

The Model Context Protocol lets an assistant call outside tools. With Augure's server connected, your assistant can hand a question or a block of text to an Augure model and use the answer. The assistant's own model keeps doing everything else.

Installing the MCP server does not replace your assistant's main model and does not change its provider's data policy. If you want Augure as the main model, use the OpenAI-compatible API in your IDE or with Augure Code.

Availability: open to any Augure developer account with a card on file, once MCP is enabled in the developer dashboard. The server speaks Streamable HTTP and authenticates by MCP key (a bearer header). Assistants that only support OAuth sign-in, such as claude.ai and ChatGPT connectors, are not supported. Claude Code 2.1.283 was verified on September 26, 2026, and is the only verified client. Other MCP clients have not been verified.

Quickstart

Create a developer account with a card on file in the developer dashboard. MCP usage is billed to that account.
Select Enable MCP in the dashboard. This switches the account to threshold billing (see Pricing below).
Create an MCP key (aug_mcp_live_…). Choose the tools it may call and an expiry. The secret is shown once.
Add the server to your client (below), pasting the key where the placeholder is.
Call list_models, then ask_augure.

Claude Code

terminal

claude mcp add --transport http augure https://mcp.augureai.ca/mcp \
  --header "Authorization: Bearer aug_mcp_live_…"

First ask_augure call

ask_augure

{
  "prompt": "Reply with exactly MCP_OK",
  "model": "rosedale-1",
  "reasoning_effort": "low",
  "max_output_tokens": 256
}

Keep the key out of shared files. Use your client's secret input or an environment variable where it offers one, and never commit an MCP key to a project repository. Rotate it from the dashboard if it leaks; the old secret stops working within a minute.

Before the first paid call: ask_augure is billed per token. list_models and get_limits are free.

Tools

Three tools are released, and one model: rosedale-1. Each key holds an explicit subset; a tool the key was not granted is neither listed nor callable. Web search and document reading are on the roadmap and are not available.

ask_augureBilled per token

Sends a text prompt, with optional text context, to an Augure model and returns the answer with usage and the model actually served.

Arguments: prompt (required, non-blank, up to 100,000 characters) · context (up to 200,000 characters) · model (rosedale-1) · reasoning_effort (low, medium or high) · max_output_tokens (≤ 8,192)

list_modelsFree

The model ids and supported reasoning_efforts this key can use with ask_augure. Call it first.

Arguments: none

get_limitsFree

Billing status, today's spend against the ceiling, call limits, the tools this key holds and its residency policy. Works even when billing is inactive, so it can explain a refusal.

Arguments: none

Results carry both readable text and a structured payload (answer, model requested and served, token usage, request id, inference region). Answers over 32,000 characters are truncated with an explicit marker. The truncated field is also true when finish_reason is length. Limits: 30 tool calls per minute per key; two paid calls in flight per account.

Pricing

MCP uses your Augure developer billing account. Connecting, listing models and checking limits are free. Model calls are billed at the applicable input and output token rates for the model served, exactly as through the REST API. There is no MCP connection fee and no separate plan.

Enabling MCP switches your developer account to threshold billing: your card is charged each time usage reaches C$50, or at month end, whichever comes first. If your developer account already existed, usage to date is invoiced right away on a final invoice for the old billing period, then threshold billing starts.

Your assistant provider's charges are separate.
Augure app-plan credits do not apply.
Reasoning tokens are billed as output on models that reason; the visible answer alone is not the whole generation. The tool always states a reasoning effort (default low).
A call refused before execution (authentication, schema, billing, budget) costs nothing. A timeout or lost response after generation started may still be billed.
Usage appears in the developer dashboard with the rest of your API usage.

See the API rate card →

Where your data goes

Text you send through a tool is processed by Augure in Canada. Model inference for MCP runs on rosedale-1, served on Augure's Canadian capacity in Ontario. If that capacity is busy, the call can be served by a second Augure deployment in Ontario, which may use a different model; the result then shows fallback: true. MCP calls are Canada-only: if no Canadian capacity is available, the call fails with canadian_capacity_unavailable rather than leaving Canada. The result reports the inference region so you can check.

Your connected assistant receives both the context you send and the results Augure returns, under that assistant provider's terms. Connecting Augure does not change where your assistant's own model runs or what it sees.

Augure logs tool name, key id, sizes and timings. It does not log prompts, context or answers.

Errors and what to do

Code	Next action
403 mcp_billing_setup_required	MCP is not enabled on this account yet. Enable MCP in the developer dashboard first, then create an MCP key.
canadian_capacity_unavailable	Canadian capacity is unavailable right now. MCP calls are Canada-only, so the call fails instead of being served outside Canada. Retry later.
unsupported_reasoning_effort	rosedale-1 supports low (default), medium and high over MCP. none is not supported and is refused before generation, without charge.
empty_completion / reasoning_cutoff	No answer was delivered; this turn is not charged. Increase a tiny output budget or reduce effort. This is not a capacity-outage signal.
concurrency_limit_exceeded	Two paid calls are already in flight for this account. Wait for a call to finish.
401	Missing, invalid, revoked or expired key. Create or rotate one in the developer dashboard.
403 mcp_key_not_allowed	You sent an MCP key to the REST API. MCP keys work only with the MCP server; use a developer key (aug_sk_live_…) for direct API calls.
billing_inactive	Add or update a payment method in the developer dashboard. Free tools keep working.
model_unavailable / model_not_available	No model is enabled for this key yet, or the id is not on list_models.
quota_exceeded	Today's spend ceiling is reached. It resets at 00:00 UTC.
budget_unavailable	Augure could not verify your spend budget; nothing was charged. Retry in ~30 s.
rate_limited	Too many calls this minute. The result carries retry_after_s.
timeout_or_cancelled	The call exceeded its deadline or was cancelled. A generation already under way may still have been billed; do not auto-retry blindly.