Skip to main content

​
Alpic architecture overview

To allow zero-configuration deployments of MCP servers and Apps that scale with your users, Alpic uses a serverless architecture. Alpic exposes an MPC gateway that handles protocol-specific specificities like transport and authentication, and proxies requests to the MCP server built from your connected repository. This means that your repository needs to expose an MCP server endpoint that can be accessed by the Alpic gateway, either locally in stdio, or via SSE or Streamable HTTP.

​
Public Endpoints

All deployed servers are hosted by default on domains in the form of https://my-domain-123456.alpic.live. Each environment receives its own unique domain that you can use to connect your MCP clients. Here is the list of available endpoints on your MCP server domain:
  • / - Main MCP Server Endpoint. It supports both SSE and StreamableHTTP transports.
  • /mcp - it supports StreamableHTTP transport only and is used for compatibility with certain MCP Clients.
  • /try - The Playground, an AI-powered interface where users can try your MCP server directly from their browser.

​
Supported MCP protocol versions

Alpic serves 2026-07-28 only to clients whose name starts with openai-mcp. Other clients sending 2026-07-28 get a 400 and fall back to initialize. If your server doesn’t support 2026-07-28, its server/discover fails and Alpic answers it with a 400, so the client falls back to initialize too.

​
Events

  • Alpic forwards the events capability and events/list, events/subscribe and events/unsubscribe to your server, but stores and delivers nothing. Keep subscriptions in your own storage and deliver events from a separate process outside Alpic.
  • Your server must use Streamable HTTP: on stdio, it never receives the user’s headers, so it can’t tie a subscription to a user.
  • events/subscribe, callback verification included, is subject to the per-request time limit.

​
Internal Endpoints

The following endpoints are used internally by Alpic for authentication and server management.

​
OAuth Authentication Endpoints

These endpoints are only available if your server is not public and requires authentication:
  • /.well-known/oauth-protected-resource: Part of the OAuth authentication flow, provides metadata about protected resources
  • /.well-known/oauth-authorization-server: Part of the OAuth authentication flow. Only available if authentication is not delegated to an external authorization server

​
Dynamic Client Registration (DCR) Proxy Endpoints

The MCP 2026-07-28 spec deprecates Dynamic Client Registration in favor of Client ID Metadata Documents (CIMD). DCR remains supported as a fallback for at least 12 months.
These endpoints are only available if Dynamic Client Registration (DCR) proxy is activated:
  • /oauth2/register: Endpoint for client registration
  • /oauth2/authorize: OAuth authorization endpoint
  • /oauth2/token: OAuth token endpoint
  • /oauth2/callback: OAuth callback endpoint

​
Static Assets

/assets: Static assets exposed by your MCP server. This endpoint serves any static files you’ve configured for deployment in your repository. Learn more about how static assets are generated and served by Alpic in our guide on Hosting ChatGPT Apps.