MCP Setup
MCP Setup is where servers get registered and connected. For each server:
- Add MCP server registers the target (admin-only).
- Connect SDK analytics mints the server’s ingest key — shown once, then identified by its region-marked prefix (
ami_us_… / ami_eu_…). The dialog also shows your region’s ingest URL: set both as ANALYTICS_INGEST_API_KEY and ANALYTICS_INGEST_URL in that server’s deployment and instrument it with the SDK. EU workspaces must keep the URL — the SDK defaults to the US endpoint.
- Each key card shows its prefix, creation time, call count, and last-used time. Rotate issues a replacement; Revoke stops ingestion immediately.
One ingest key per server keeps rotation blast-radius small and attribution clean.
API keys
Settings → API keys manages your workspace’s Armature API keys — used to connect outbound, for example authenticating your coding agent against the Armature MCP or triggering eval runs from CI. Keys are shown once at creation.
The two key types differ by direction: ingest keys let your servers send data into Armature, and API keys let your tools read analytics out of Armature and trigger eval runs.
Usage
Settings → Usage shows sessions used this month against your plan’s monthly limit, plus your data retention window. On the Free plan the sidebar also shows a live session meter.
If you pass the monthly limit, nothing is dropped — new sessions are still captured; the dashboard shows an over-limit banner and history is limited to your retention window. For higher limits and longer retention, use the Upgrade plan contact link or see pricing.
Team
Invite teammates from the account menu (Invite team members). Organization details and your profile live under Settings → Organization and Profile.
