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

# MCP (Model Context Protocol)

> Query and manage Holos skills directly from Claude, ChatGPT, Gemini, and other AI assistants.

<Note>
  Holos MCP support is in development. This page describes what we're building. Reach out if you'd like to be an early tester.
</Note>

The [Model Context Protocol](https://modelcontextprotocol.io) (MCP) is an open standard that lets AI assistants connect directly to external tools and data. A Holos MCP server means your organization's skill library becomes queryable and writable from Claude, ChatGPT, Gemini, or any other MCP-compatible assistant, without leaving the tools your team already uses.

## What you'll be able to do

<CardGroup cols={2}>
  <Card title="Query skills" icon="magnifying-glass">
    Ask your AI assistant which skills exist, what their status is, who's assigned, and what's overdue, all in plain language.
  </Card>

  <Card title="Create skills" icon="plus">
    Draft a new skill with a title, instructions, assignees, and a deadline directly from a chat prompt.
  </Card>

  <Card title="Trigger captures" icon="circle-dot">
    Kick off a capture workflow without switching to the Holos dashboard.
  </Card>

  <Card title="Retrieve outputs" icon="file-lines">
    Pull generated SOPs, course outlines, and training content into your AI session for review or further editing.
  </Card>
</CardGroup>

## Authentication

The Holos MCP server uses an OAuth 2.1-compliant authorization flow built on the same identity infrastructure that powers your existing Holos sessions. When you connect an AI assistant for the first time:

1. **Authorization request.** Your AI assistant initiates an OAuth 2.1 authorization request.
2. **One-time approval.** You complete a single browser prompt using the same passwordless flow you use to log in to Holos. Permissions are presented in plain language so you know exactly what access you're granting.
3. **Scoped access token.** The assistant receives a short-lived token with only the permissions you approved. An assistant can never be granted more access than you yourself have.

## Security

Access is controlled at both the user and organization level:

* **RBAC scopes.** Permissions are structured in logical sets so agents get only the access they need, nothing more.
* **Org-level controls.** Admins get a centralized view of all connected assistants, authorized scopes, and active sessions across the organization.
* **Allowlists.** Organizations can restrict which AI assistants members are permitted to connect.
* **One-click revocation.** Any connected assistant can be disconnected instantly from your account settings or by an org admin.
* **Audit trail.** A real-time log of all connected apps and the scopes they've been granted.

## Interested in early access?

We're evaluating MCP support now. If you have a specific integration in mind or want to be among the first to try it, [let us know](mailto:hello@holos.io).