apollographql
diff --git a/‎.github/workflows/templates-test.yml‎
Lines changed: 8 additions & 3 deletions b/‎.github/workflows/templates-test.yml‎
Lines changed: 8 additions & 3 deletions
diff --git a/‎.github/workflows/test.yml‎
Lines changed: 1 addition & 1 deletion b/‎.github/workflows/test.yml‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎.gitleaks.toml‎
Lines changed: 31 additions & 0 deletions b/‎.gitleaks.toml‎
Lines changed: 31 additions & 0 deletions
diff --git a/‎CHANGELOG.md‎
Lines changed: 18 additions & 2 deletions b/‎CHANGELOG.md‎
Lines changed: 18 additions & 2 deletions
diff --git a/‎CONTRIBUTING.md‎
Lines changed: 7 additions & 7 deletions b/‎CONTRIBUTING.md‎
Lines changed: 7 additions & 7 deletions
diff --git a/‎add-mcp/.apollo/mcp.local.yaml‎
Lines changed: 47 additions & 0 deletions b/‎add-mcp/.apollo/mcp.local.yaml‎
Lines changed: 47 additions & 0 deletions
diff --git a/‎add-mcp/.apollo/mcp.staging.yaml‎
Lines changed: 62 additions & 0 deletions b/‎add-mcp/.apollo/mcp.staging.yaml‎
Lines changed: 62 additions & 0 deletions
diff --git a/‎add-mcp/.env.template‎
Lines changed: 29 additions & 0 deletions b/‎add-mcp/.env.template‎
Lines changed: 29 additions & 0 deletions
diff --git a/‎add-mcp/.gitignore‎
Lines changed: 32 additions & 0 deletions b/‎add-mcp/.gitignore‎
Lines changed: 32 additions & 0 deletions
@@ -20,14 +20,19 @@ jobs:
         cache: 'npm'
 
     - name: Install dependencies
-      run: npm ci
+      run: npm i
 
     - name: Test TypeScript template
       run: |
         echo "Testing TypeScript template..."
-        npm run test:template start-with-typescript "npm ci" "npm test"
+        npm run test:template start-with-typescript "npm i" "npm test"
 
     - name: Test REST template
       run: |
         echo "Testing REST template..."
-        npm run test:template start-with-rest "echo \"REST template test coming soon\""
+        npm run test:template start-with-rest "echo \"REST template test coming soon\""
+
+    - name: Test MCP template
+      run: |
+        echo "Testing MCP template..."
+        npm run test:template add-mcp "echo \"Testing MCP augmentation template\""
@@ -20,7 +20,7 @@ jobs:
         cache: 'npm'
 
     - name: Install dependencies
-      run: npm ci
+      run: npm i
 
     - name: Run manifest validation
       run: |
 
@@ -0,0 +1,31 @@
+# Gitleaks configuration for allowlisting detected secrets
+# These secrets were detected in files that no longer exist but the commits remain
+
+[[rules]]
+id = "curl-auth-header"
+[rules.allowlist]
+commits = [
+    "37bbb045e7c4cbda32ed9894e53475553da83a0b",
+    "dd01efc558aac6cb3724f46cc5b97a124dde78e3",
+    "0ddbd71c1d29609e9c9901fe9ca1d41ac92fdf9a",
+    "0d722f28d74020dd8a09f2f7b736fd39e745c4ab",
+    "5035981f16d73efc604e91694cd9f8daa904d19c",
+    "9e1c6ae02233a1f5d2578fed8cbca4788454e7ca",
+    "4cd4925cc010f68c913a72a3fa89fe08ac0b17d6",
+    "7c0de7af3c23f56d379c488c1ea1b056b158818d",
+    "61996d7dcbe79a6688eb51ced0db65161729eaf2"
+]
+
+[[rules]]
+id = "apollo-graphos-api-key"
+[rules.allowlist]
+commits = [
+    "37bbb045e7c4cbda32ed9894e53475553da83a0b",
+    "dd01efc558aac6cb3724f46cc5b97a124dde78e3",
+    "0ddbd71c1d29609e9c9901fe9ca1d41ac92fdf9a",
+    "0d722f28d74020dd8a09f2f7b736fd39e745c4ab",
+    "5035981f16d73efc604e91694cd9f8daa904d19c",
+    "9e1c6ae02233a1f5d2578fed8cbca4788454e7ca",
+    "4cd4925cc010f68c913a72a3fa89fe08ac0b17d6",
+    "61996d7dcbe79a6688eb51ced0db65161729eaf2"
+]
@@ -2,13 +2,29 @@
 
 All notable changes to this project will be documented in this file.
 
-## [v1] - 2025-05-12
+## [v2.0.0] - 2025-09-30
+
+### Added
+- **NEW**: MCP (Model Context Protocol) server template (`add-mcp/`)
+  - Enables AI assistants to access GraphQL APIs
+  - Includes Docker support and VSCode configuration
+  - Quick GraphQL-to-AI integration setup
+- Enhanced `.gitignore` files across templates
+- `.vscode/settings.json` and `.vscode/tasks.json` configuration files
+
+### Breaking Changes
+- **BREAKING**: Standardized template file naming:
+  - `products.graphql` → `schema.graphql`
+  - `getting-started.md` → `GETTING_STARTED.md`
+- Migration guide: Update your template references to use new file names
+
+## [v1.0.0] - 2025-05-12
 
 ### Added
 - start-with-typescript template
 - Schema validation and print_depth support in manifest
 - Template test workflow and schema validation in CI
-- Community link in getting-started.md
+- Community link in GETTING_STARTED.md
 
 ### Changed
 - Updated folder structure and manifest fields to use `commands` array
 
@@ -18,7 +18,7 @@ This document outlines the process for contributing new templates to the rover-i
    - Ensure the name is descriptive of the "starting" experience (e.g., `start-with-typescript`). Use kebab-case for folder names.
 
 2. Required Artifacts (must-have items for every starter):
-   - **Getting started documentation**: A `getting-started.md` file (or custom name, see `start_point_file` below). This file should explain what the starter is, how to use it, and any educational context.
+   - **Getting started documentation**: A `GETTING_STARTED.md` file (or custom name, see `start_point_file` below). This file should explain what the starter is, how to use it, and any educational context.
    - **Project files**: All files needed for the starter to build and run (e.g., `package.json`, source files, configs).
    - **Test files**: Include tests to verify the starter works as intended.
    - **Manifest fields mapping**: Ensure your starter provides the following, which will be referenced in `manifest.json`:
@@ -42,11 +42,11 @@ This document outlines the process for contributing new templates to the rover-i
   "id": "typescript",
   "display_name": "Start with TypeScript",
   "path": "start-with-typescript",
-  "commands": ["npm ci", "npm run dev"],
+  "commands": ["npm i", "npm run dev"],
   "language": "TypeScript",
   "federation_version": "=2.10.0",
   "max_schema_depth": 5,
-  "test_commands": ["npm ci", "npm test"],
+  "test_commands": ["npm i", "npm test"],
   "routing_url": "http://localhost:4001",
   "print_depth": 2
 }
@@ -74,11 +74,11 @@ Each template must include the following in `manifest.json`:
 | routing_url      | String       | URL where the subgraph is exposed                                          |
 | max_schema_depth | Int (optional) | Maximum depth for GraphQL file discovery (defaults to 5)                  |
 | print_depth      | Int (optional) | Controls file display depth during init execution                         |
-| start_point_file | String (optional) | Custom name for the "getting started" documentation file (defaults to `getting-started.md`) |
+| start_point_file | String (optional) | Custom name for the "getting started" documentation file (defaults to `GETTING_STARTED.md`) |
 
 
 Required files:
-- Getting started documentation (default: `getting-started.md`)
+- Getting started documentation (default: `GETTING_STARTED.md`)
 - All necessary project files (`package.json`, source files, etc.)
 - Test files to verify the starter works
 
@@ -87,7 +87,7 @@ Required files:
 When making breaking changes to existing templates:
 
 1. Clearly document the changes in your PR description.
-2. Update the template's getting-started documentation to reflect the changes.
+2. Update the template's GETTING_STARTED documentation to reflect the changes.
 3. If removing or updating `manifest.json` fields:
    - Document any removed or changed fields.
    - Provide migration steps if applicable.
@@ -110,7 +110,7 @@ When making breaking changes to existing templates:
 - Follow the existing code style in the repository.
 - Ensure all files are properly formatted.
 - Run linting tools (e.g., ESLint, Prettier) before submitting your PR.
-- Maintain consistent documentation style in getting-started files.
+- Maintain consistent documentation style in GETTING_STARTED files.
 - Follow the established naming conventions for template folders (kebab-case).
 - Reference the repository's style guide if available.
 
 
@@ -0,0 +1,47 @@
+# Apollo MCP Server Configuration - Local Development
+# This configuration connects your GraphQL API to AI assistants via MCP
+
+# Working local configuration:
+overrides:
+  mutation_mode: all
+operations:
+  source: collection
+  id: default                   # localhost:4000 in browser → Sandbox → Collections → Create operations for MCP tools
+                                # Docs: https://www.apollographql.com/docs/apollo-mcp-server/define-tools
+introspection:
+  introspect:
+    enabled: true               # Required for AI to understand your schema
+  search:
+    enabled: true
+  execute:
+    enabled: true
+  validate:
+    enabled: true
+transport:
+  type: streamable_http
+  port: 5050                    # MCP server port
+endpoint: http://localhost:4000 # Your GraphQL API endpoint
+
+# =============================================================================
+# Configuration Details
+# =============================================================================
+
+name: "${PROJECT_NAME} GraphQL API"
+description: "GraphQL API for ${PROJECT_NAME}"
+
+# Essential settings for local development:
+# - mutations enabled for full API access
+# - introspection enabled for schema discovery
+# - tools loaded from operation collections
+# - connects to GraphQL API on port 4000
+
+# To customize:
+# 1. Create operation collections in Apollo Studio Sandbox
+# 2. Update endpoint to match your GraphQL server URL
+# 3. Run: docker build -f mcp.Dockerfile -t my-mcp-server .
+# 4. Run: docker run -p 5050:5050 --env-file .env my-mcp-server
+
+# Environment variables (optional):
+# GRAPHQL_ENDPOINT - override endpoint URL
+# MCP_PORT - override MCP server port (default: 5050)
+# PROJECT_NAME - project identifier for AI assistant
@@ -0,0 +1,62 @@
+# Apollo MCP Server Configuration - Staging Environment
+# This staging configuration provides settings with enhanced security
+
+# Working staging configuration:
+overrides:
+  mutation_mode: all
+  require_confirmation: true    # Confirmation required for mutations in staging
+operations:
+  source: collection
+  id: default                   # GraphQL endpoint in browser → Sandbox → Collections → Create operations for MCP tools
+                                # Docs: https://www.apollographql.com/docs/apollo-mcp-server/define-tools
+introspection:
+  introspect:
+    enabled: true               # Enabled for testing (disable for production)
+  search:
+    enabled: true
+  execute:
+    enabled: true
+  validate:
+    enabled: true
+transport:
+  type: streamable_http
+  port: 5050                    # MCP server port
+endpoint: "${STAGING_GRAPHQL_ENDPOINT}"  # Your staging GraphQL API endpoint
+
+# Authentication headers for staging
+headers:
+  Authorization: "Bearer ${APOLLO_KEY}"
+  X-Environment: "staging"
+  Content-Type: "application/json"
+
+# =============================================================================
+# Configuration Details
+# =============================================================================
+
+name: "${PROJECT_NAME} GraphQL API (Staging)"
+description: "Staging environment for ${PROJECT_NAME} GraphQL API"
+
+# Enhanced security settings for staging:
+# - mutations require confirmation
+# - authentication with staging API key
+# - reduced timeouts for reliability
+# - introspection enabled for testing
+
+# Key staging differences from local:
+# - Authentication required via APOLLO_KEY
+# - Mutation confirmation enabled for safety
+# - Production-appropriate logging and monitoring
+# - Stricter rate limiting and validation
+
+# To deploy staging:
+# 1. Create operation collections in Apollo Studio Sandbox
+# 2. Set STAGING_GRAPHQL_ENDPOINT to your staging GraphQL URL
+# 3. Set APOLLO_KEY for authentication
+# 4. Run: docker build -f mcp.Dockerfile -t my-mcp-staging .
+# 5. Run: docker run -p 5050:5050 --env-file .env.staging my-mcp-staging
+
+# Environment variables for staging:
+# STAGING_GRAPHQL_ENDPOINT - staging GraphQL endpoint
+# APOLLO_KEY - API key for staging authentication
+# PROJECT_NAME - project identifier
+# MCP_PORT - MCP server port (default: 5050)
@@ -0,0 +1,29 @@
+# Apollo MCP Server Environment Configuration
+#
+# SETUP: Create your .env file from this template
+#
+# Copy command (works on macOS, Linux, and Windows):
+#   cp .env.template .env
+#
+# NEVER commit .env to version control!
+
+# Your project name
+PROJECT_NAME="{{PROJECT_NAME}}"
+
+# Your GraphQL API endpoint
+GRAPHQL_ENDPOINT="{{GRAPHQL_ENDPOINT}}"
+
+# Apollo API key (if your endpoint requires authentication)
+# Get from: https://studio.apollographql.com/user-settings/api-keys
+APOLLO_KEY="{{APOLLO_KEY}}"
+
+# Apollo Graph Reference (Graph ID@Variant)
+APOLLO_GRAPH_REF="{{APOLLO_GRAPH_REF}}"
+
+# MCP Server Configuration
+MCP_ENABLE=1
+MCP_PORT=5050
+
+# Optional: Environment and logging
+NODE_ENV="development"
+LOG_LEVEL="info"
@@ -0,0 +1,32 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Node modules
+node_modules/
+
+# Mac OS
+.DS_Store
+
+# Environment variables
+.env
+.env.*
+!.env.template
+
+# Docker volumes and caches
+.docker/
+
+# IDE files
+.vscode/
+.idea/
+
+# Temporary files
+*.tmp
+*.temp
+
+# Generated files
+dist/
+build/