Alpic MCP Server for Claude

Overview

Alpic is a cloud platform for building, deploying, monitoring, and distributing ChatGPT apps and MCP servers. The Alpic MCP server lets operators manage projects hosted on Alpic—checking deployment health, debugging builds, and reviewing analytics—directly from Claude and other MCP clients.

Platform documentation is at docs.alpic.ai. The management connector is hosted at https://mcp.alpic.ai.

Features

• Manage Alpic MCP projects and environments from chat.
• Debug deployment failures and inspect build output.
• Review analytics for distributed MCP apps.
• Streamable HTTP and SSE-compatible hosted endpoint.
• Integrates with Alpic's gateway, auth, and serverless hosting.

Use Cases

• Check why a deployed MCP server failed its /mcp health check.
• Review usage analytics after launching a ChatGPT app.
• Compare staging and production deployment status.
• Trigger redeploy after fixing repository configuration.
• Audit OAuth and API-key auth settings on a hosted server.

Installation

Claude (Connectors)

1. Sign in at app.alpic.ai and deploy or link an MCP project.
2. Add https://mcp.alpic.ai as a custom MCP connector.
3. Authenticate with your Alpic account or token.
4. Invoke project management tools from Claude.

Claude Code

claude mcp add --transport http alpic https://mcp.alpic.ai
claude mcp list

Other MCP clients

Add the connector using the JSON configuration below in your MCP client settings.

Configuration

{
  "mcpServers": {
    "alpic": {
      "url": "https://mcp.alpic.ai",
      "type": "http"
    }
  }
}

For authenticated setups:

{
  "mcpServers": {
    "alpic": {
      "url": "https://mcp.alpic.ai",
      "type": "http",
      "headers": {
        "Authorization": "Bearer YOUR_ALPIC_TOKEN"
      }
    }
  }
}

Authenticate with Alpic credentials; unauthenticated calls cannot manage your projects.

Examples

Deploy status

List my Alpic MCP projects and show the latest deployment status for each.

Debug 404

Why did my Alpic deployment fail the /mcp health check?

Analytics

Summarise MCP app traffic for my production project over the last 7 days.

Security

• Confirm project and environment before redeploy or delete operations.
• Treat analytics exports as potentially containing user query metadata.
• Use separate Alpic workspaces for production and experimentation.

Troubleshooting

401 unauthorized

Re-authenticate the connector with your Alpic account.

Project not found

Verify the project ID and that your token has workspace access.

404 on managed deploy

Ensure the target server exposes /mcp as Alpic expects.

Stale analytics

Allow time for telemetry ingestion; refresh after a few minutes.

Duplicate Check

No existing Alpic management MCP entry was found in content/mcp/. This differs from generic cloud deploy MCP servers because it operates on Alpic-hosted MCP projects specifically.