# Armature

## Docs

- [Email alerts for Armature workflows and monitors](https://docs.armature.tech/alerts/email.md): Send email notifications when an Armature workflow run fails or a tool monitor fires. No integration required — just a recipient address.
- [Slack alerts for Armature workflows and monitors](https://docs.armature.tech/alerts/slack.md): Send Slack notifications when an Armature workflow run fails or a tool monitor fires. Configure alert rules per channel or user in a few steps.
- [Key concepts in Armature: workflows, runs, and more](https://docs.armature.tech/concepts.md): The vocabulary you need to use Armature effectively: MCP servers, workflows, runs, criteria, monitors, coverage, versions, policies, alerts, and API keys.
- [Armature: Continuous MCP Server Testing and Monitoring](https://docs.armature.tech/introduction.md): Armature runs scheduled AI-agent workflows against your MCP servers, monitors tool health, and alerts your team when something breaks or regresses.
- [Authenticating with the Armature MCP API](https://docs.armature.tech/mcp-api/authentication.md): Use Armature API keys to authenticate MCP clients. Keys are org-scoped, role-frozen at creation, and passed as Bearer tokens in the Authorization header.
- [Armature MCP API structured error codes reference](https://docs.armature.tech/mcp-api/errors.md): Structured JSON-RPC error codes returned by Armature MCP tools—with causes, affected operations, and remediation steps for each code.
- [Armature MCP API for agent-driven testing](https://docs.armature.tech/mcp-api/overview.md): Connect any MCP client to Armature to triage failing runs, propose workflow repairs, trigger validations, and inspect MCP coverage from one endpoint.
- [MCP prompts for workflow repair and authoring](https://docs.armature.tech/mcp-api/prompts.md): Use Armature MCP prompts to start structured repair and coverage-driven authoring sessions—with sequenced steps that guide agents through each workflow.
- [MCP resources: run traces, schemas, catalogs](https://docs.armature.tech/mcp-api/resources.md): Read structured Armature data—run traces, artifacts, workflow schemas, coverage reports, and staged proposals—using addressable armature:// URIs.
- [MCP API permissions: viewer, editor, admin, owner](https://docs.armature.tech/mcp-api/roles.md): Armature enforces viewer, editor, admin, and owner roles on the MCP endpoint. Key roles are frozen at creation and determine which tools an agent can call.
- [Repair workflow tools: propose and apply changes](https://docs.armature.tech/mcp-api/tools/repair.md): Stage workflow patches, draft regression workflows from failed runs, and apply approved changes — the full agent-driven repair loop.
- [Run and sync tools: trigger runs and catalog sync](https://docs.armature.tech/mcp-api/tools/runs.md): Dispatch manual workflow runs with idempotent keys, compare run results across versions, and refresh your MCP server tool catalog.
- [Triage MCP tools: search, inspect, diagnose](https://docs.armature.tech/mcp-api/tools/triage.md): Read-only tools for searching workflow runs, inspecting run details, diagnosing failures, and reviewing organization health — available to all roles.
- [Connect and configure an MCP server in Armature](https://docs.armature.tech/mcp-servers/connecting.md): Register an MCP server with Armature by providing its URL and auth credentials. Armature probes it live and discovers all available tools automatically.
- [View and close MCP server tool coverage gaps](https://docs.armature.tech/mcp-servers/coverage.md): See which tools in your MCP server catalog are exercised by Armature workflows and which are untested, so you can close gaps before they become incidents.
- [MCP tool monitors: per-tool health checks](https://docs.armature.tech/mcp-servers/tool-monitors.md): Set up recurring pings for individual MCP tools so Armature alerts you the moment a tool starts failing, timing out, or becoming unreachable.
- [Get started with Armature: your first workflow and monitor](https://docs.armature.tech/quickstart.md): Connect your first MCP server, create a tool monitor, write your first workflow, and view the results — end to end in a few minutes.
- [Create and manage Armature API keys for MCP access](https://docs.armature.tech/settings/api-keys.md): Create and manage bearer tokens that authenticate MCP clients with Armature. Each token is shown once and cannot be retrieved after creation.
- [Manage your Armature subscription and billing plan](https://docs.armature.tech/settings/billing.md): Manage your Armature subscription, switch plans or billing periods, and handle cancellations or refunds. Billing is available to workspace owners only.
- [Managing your Armature team and invitations](https://docs.armature.tech/settings/team.md): Invite team members, assign roles, and manage pending invitations in your Armature workspace. Admins and owners can invite by email or shareable link.
- [Authoring effective Armature test workflows](https://docs.armature.tech/workflows/authoring.md): Write prompts and criteria that produce reliable, repeatable MCP server test runs — covering tool policy, run-scoped data, and regression drafts.
- [Armature Workflows: Automated MCP Server Testing](https://docs.armature.tech/workflows/overview.md): Workflows are scheduled AI-agent tests that continuously verify your MCP server behavior. Learn how to create, filter, and track them from the dashboard.
- [Understanding Armature workflow run results](https://docs.armature.tech/workflows/runs.md): Interpret pass, partial, fail, and error statuses for workflow runs. Inspect tool-call traces, filter by time range, and compare runs to spot regressions.
- [Schedule and trigger Armature test workflows](https://docs.armature.tech/workflows/schedules.md): Set up automatic cron schedules, manual-only triggers, and on-demand runs for your Armature test workflows — including how to pause and resume safely.