> ## Documentation Index
> Fetch the complete documentation index at: https://docs.armature.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace & settings

> Servers, keys, usage, and your team

## 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 prefix. Set it as `ANALYTICS_INGEST_API_KEY` in that server's deployment and instrument it with the SDK.
* Each key card shows its prefix, creation time, call count, and last-used time. **Rotate** issues a replacement; **Revoke** stops ingestion immediately.

<Note>
  One ingest key per server keeps rotation blast-radius small and attribution clean.
</Note>

## 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](/armature-mcp/connect). Keys are shown once at creation.

The two key types in one line: **ingest keys** let your servers send data *into* Armature; **API keys** let your tools read analytics *out of* Armature.

## Usage

**Settings → Usage** shows sessions used this month against your plan's allowance, plus your data retention window. On the Free plan the sidebar also shows a live session meter.

If you pass the monthly allowance, **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](https://armature.tech/#pricing).

## Team

Invite teammates from the account menu (**Invite team members**). Organization details and your profile live under **Settings → Organization** and **Profile**.