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

# Overview

> Secure your MCP servers with flexible authentication options on Alpic

Alpic supports many different authentication options for your MCP servers, from simple public access to enterprise-grade OAuth integration.

By default, servers deployed on Alpic are **public** and accessible to anyone with the server URL.

## Authentication Options

If you want to protect your server with authentication, you have two main options:

<CardGroup cols={2}>
  <Card title="OAuth Authentication" href="/secure/auth/oauth-setup" icon="shield">
    Integrate with identity providers using OAuth.
  </Card>

  <Card title="API Key Protection" href="/secure/auth/token-bearer-setup" icon="key">
    Protect your server with API keys via custom headers.
  </Card>
</CardGroup>

<Tip>
  Alpic itself is not an authentication provider or IdP, but is compatible with all authentication options above. You
  implement authentication in your MCP server code, and Alpic will host and serve your protected server.
</Tip>