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

# Pleo MCP Enablement Overview

> Choose your AI platform to enable the Pleo MCP for your organisation, and check whether any admin action is needed at all.

export const RememberCallout = ({title, children, icon = "🪢"}) => <div style={{
  backgroundColor: 'var(--recommended-bg)',
  borderLeft: '4px solid #f63b92',
  borderRadius: '10px',
  padding: '18px 22px',
  marginBottom: '20px',
  boxShadow: '1px 1px 3px rgba(0,0,0,0.06)'
}}>
    <div style={{
  display: 'flex',
  alignItems: 'flex-start',
  gap: '14px'
}}>
      <span style={{
  fontSize: '22px',
  lineHeight: '1',
  flexShrink: 0
}}>
        {icon}
      </span>
      <div>
        {title && <div style={{
  fontSize: '16px',
  fontWeight: 600,
  color: 'var(--recommended-title)',
  marginBottom: '6px'
}}>
            {title}
          </div>}
        <div style={{
  fontSize: '14px',
  lineHeight: 1.65
}}>
          {children}
        </div>
      </div>
    </div>
  </div>;

Enablement is the **organisation-level** step that allows members to add the Pleo MCP in their AI platform.

Whether you need it depends on your plan: individual plans (such as Claude Pro or ChatGPT Plus) usually need no admin action, while managed workspaces and tenants often restrict custom connectors until an admin allows them.

## Prerequisites

<RememberCallout title="Remember">
  Enablement in your AI platform is separate from enablement in Pleo. A company admin must also enable MCP access in Pleo before anyone can connect. See [Access & Permissions](/docs/current/pleo-mcp/get-started/access-and-permissions).
</RememberCallout>

## Find Your Enablement Guide

These guides walk an **admin** through enabling the Pleo MCP at the **organisation level**, so individual members can then connect it themselves.

Select your AI platform below for the relevant enablement steps.

<CardGroup cols={2}>
  <Card title="Claude" icon="message" href="/docs/current/pleo-mcp/how-tos/enablement/claude">
    <div className="text-sm mt-2">Add Pleo as an organisation-wide custom connector in Claude for Work.</div>
  </Card>

  <Card title="Codex" icon="terminal" href="/docs/current/pleo-mcp/how-tos/enablement/codex">
    <div className="text-sm mt-2">Where org-level control actually lives for Codex, which has no admin console of its own.</div>
  </Card>

  <Card title="ChatGPT" icon="comments" href="/docs/current/pleo-mcp/how-tos/enablement/chatgpt">
    <div className="text-sm mt-2">Enable custom connectors for a ChatGPT Business, Enterprise, or Edu workspace.</div>
  </Card>

  <Card title="Gemini Enterprise" icon="sparkles" href="/docs/current/pleo-mcp/how-tos/enablement/gemini-enterprise">
    <div className="text-sm mt-2">Register Pleo as a Custom MCP Server in Google Cloud.</div>
  </Card>

  <Card title="Microsoft Copilot" icon="microsoft" href="/docs/current/pleo-mcp/how-tos/enablement/copilot">
    <div className="text-sm mt-2">Approve Pleo as an allowed MCP server for Copilot Studio agents.</div>
  </Card>
</CardGroup>

***

## What Comes Next?

* [Pleo MCP Installation Overview](/docs/current/pleo-mcp/how-tos/installation/overview)

***

## Related Reading

* [Access & Permissions](/docs/current/pleo-mcp/get-started/access-and-permissions)
* [FAQs](/docs/current/pleo-mcp/get-started/faq)

***