@@ -80,14 +80,14 @@ docker run \
80
80
81
81
## When to choose which option?
82
82
83
- | Scenario | Recommended Option | Why |
84
- | --------------------------------------- | ---------------------------- | --------------------------------------------------------- |
85
- | ** New GraphQL + MCP deployment** | ** Apollo Runtime Container** | Single container, easier to manage, optimized performance |
86
- | ** Adding MCP to existing GraphQL API ** | Standalone Apollo MCP Server | Connect to your existing GraphQL endpoint |
87
- | ** GraphOS managed graph ** | ** Apollo Runtime Container ** | Automatic schema/PQ sync, unified telemetry |
88
- | ** Local development ** | Either option works | Choose what matches your production setup |
89
- | ** Kubernetes/orchestrated environment ** | ** Apollo Runtime Container ** | Fewer moving parts, simpler networking
90
-
83
+ | Scenario | Recommended Option | Why |
84
+ | ----------------------------------- | ---------------------------- | ------------------------------------------------ --------------------------------------------------------- |
85
+ | New GraphQL + MCP deployment | Apollo Runtime Container | Single container, easier to manage, optimized performance |
86
+ | GraphOS-managed graph | Apollo Runtime Container | Automatic sync for schema and persisted queries, unified telemetry |
87
+ | Kubernetes/orchestrated environment | Apollo Runtime Container | Fewer moving parts, simpler networking |
88
+ | Adding MCP to existing GraphQL API | Standalone Apollo MCP Server | Connect to your existing GraphQL endpoint |
89
+ | Local development | ` rover dev ` | [ Run ` rover dev ` ] ( /apollo-mcp-server/run#with-the-rover-cli ) to develop locally with both GraphQL and MCP |
90
+
91
91
## Production Considerations
92
92
93
93
### Load Balancing & Session Affinity
0 commit comments