Skip to main content
When you deploy your MCP server to Alpic, the platform automatically analyzes your project to detect configuration and build requirements. This ensures your server is configured correctly without any manual setup.

​
Build Configuration

Alpic automatically detects your MCP framework, build commands, and transport type from your repository. You can customize build settings in your project configuration if needed.
Alpic detects configuration from your project source code. Most projects work out of the box without additional configuration.

​
Transport Sourcing During Deployment

Alpic automatically detects which transport type your MCP server uses by analyzing your project source code. Detection follows a priority order, using the first match found:

​
xmcp.config.ts configuration file (highest priority)

If xmcp.config.ts exists:
  • http: → streamablehttp
  • stdio: → stdio

​
TypeScript imports

Searches for imports from @modelcontextprotocol/sdk/server/:
  • stdio → stdio
  • sse → sse
  • streamableHttp → streamablehttp

​
Python mcp.run() or mcp.http_app() calls

Searches for explicit transport parameters:
  • transport="stdio" → stdio
  • transport="sse" → sse
  • transport="streamable-http" → streamable-http
  • transport="http" → http

​
Python mcp.run() fallback (lowest priority)

If mcp.run() is found without an explicit transport → defaults to stdio

​
Troubleshooting

​
Build Fails: “No MCP transport found”

If Alpic cannot detect a transport type, the build will fail. To resolve:
  1. Create an xmcp.config.ts file with your transport type
  2. Ensure you’re importing from the correct MCP SDK path (TypeScript)
  3. Add an explicit transport parameter to mcp.run() (Python)
Make sure your project uses one of the supported MCP frameworks. Alpic automatically detects transport for projects using the official MCP SDKs.