# Distribute

The Distribute section of the dashboard gets tools into the hands of the organization. Sources become hosted MCP servers with controlled visibility and per-server team access; skills and servers bundle into plugins published to agent marketplaces; and shared environments keep the secrets they need centralized.

## Sections

### [MCP Servers](/docs/ai-control-plane/distribute/mcp-servers)

Host sources as MCP servers. Each server has a copyable MCP URL and a hosted installation page, usage metrics, tool curation, OAuth configuration, visibility controls (disabled, private, or public), publishing to collections, and a per-server team access view showing exactly who can read, write, and connect.

### [Skills](/docs/ai-control-plane/distribute/skills)

Record, inspect, and version the skills available to the project. Every manifest version is kept with diffs, and skills distribute to agents by being bundled into plugins.

### [Plugins](/docs/ai-control-plane/distribute/plugins)

Bundle MCP servers and skills into distributable plugins. Assign them to roles, and publish them to Claude Code, Cursor, and Codex marketplaces through a GitHub-backed marketplace with per-client install instructions.

### [Environments](/docs/ai-control-plane/distribute/environments)

Reusable configuration and secret sets shared across MCP servers. Sensitive values stay masked and centralized instead of living in individual client configurations.

## Also in Distribute

An **Assistants** surface (beta) is rolling out for deploying governed assistants to Slack — each one connecting through the MCP servers and skills the organization already uses, with identity, guardrails, and audit built in. Organization-level distribution controls — team membership and invites, and the roles that gate who can access which servers and tools — live in the organization settings.