Skip to content

Conversation

@jonathannorris
Copy link
Member

Sets up a separate development environment for testing mcp-worker changes before production deployment.

Key Changes

  • Development worker: devcycle-mcp-server-dev with mcp-dev.devcycle.com route
  • Isolated resources: Separate durable objects and KV namespace for dev environment
  • Environment variables: Development-specific configuration (NODE_ENV=development)
  • Deploy script: Added yarn deploy:dev for easy development deployment

Benefits

✅ Safe testing environment isolated from production
✅ Separate deployment pipeline for development changes
✅ Same configuration structure as production for consistency

Usage

# Deploy to development
yarn deploy:dev

# Test at
https://mcp-dev.devcycle.com

This enables safer development and testing workflows without affecting the production MCP server.

@jonathannorris jonathannorris requested a review from a team as a code owner August 15, 2025 20:55
@JamieSinn
Copy link
Member

Did you add a dev auth0 client?

@jonathannorris
Copy link
Member Author

@JamieSinn yea different keys and application for this.

@jonathannorris jonathannorris merged commit 517c754 into main Aug 18, 2025
8 checks passed
@jonathannorris jonathannorris deleted the feat-dev-environment-setup branch August 18, 2025 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants