# Gitpod MCP > Gitpod connects your AI agent directly to cloud development environments. Use this MCP to automatically create, start, stop, and manage entire workspaces for any repository. You can also handle organization settings, update environment variables, and audit team activity without touching a dashboard. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Tags:** cloud-ide, development-environments, automation, workspace-management, remote-development, ci-cd ## Description Your agent uses Gitpod to orchestrate complex development workflows through natural language commands. Instead of manually spinning up a dev machine or updating shared configuration files in a web UI, you tell your AI client exactly what needs to happen—like starting a workspace for a specific pull request URL. This MCP lets you manage the entire lifecycle: from creating a new organization and adding members to getting detailed audit logs on who used which environment. It’s about controlling the infrastructure of development itself. You can list all existing organizations, get details on their settings, or even delete an old workspace when the project wraps up. When you connect this MCP via Vinkius, your agent gains a full view of your cloud IDE assets, making devOps tasks feel like simple chat commands. ## Tools ### create_and_start_workspace Starts an active cloud development environment from scratch. ### create_configuration Sets up a new set of rules and settings for a specific repository in Gitpod. ### create_environment_variable Adds a necessary secret or setting, like an API key, to a repository configuration. ### create_organization Establishes a new container for multiple teams and projects within Gitpod. ### delete_configuration Removes an old, unused set of rules from a repository configuration. ### delete_environment_variable Clears out an environment variable that is no longer needed for development. ### remove_organization_member Removes a user's access and membership from a Gitpod organization. ### delete_organization Completely deletes an entire Gitpod organization structure. ### delete_workspace Shuts down and removes a specific, active development workspace. ### get_configuration Retrieves all the details about an existing repository configuration to review its settings. ### get_organization_settings Gets a full report of the operational settings for a specific Gitpod organization. ### get_organization Fetches general details about an entire Gitpod organization, like its name and owner. ### get_workspace Retrieves the status and details of a specific workspace by its ID. ### join_organization Adds the current user to an organization using an invitation or access ID. ### list_audit_logs Provides a history of all actions taken within an enterprise Gitpod organization (requires Enterprise plan). ### list_configurations Shows a list of every repository configuration that exists inside an organization. ### list_environment_variables Displays all environment variables currently set for a specific repository configuration. ### list_organization_members Lists every user and their current role within the organization. ### list_organizations Returns a list of all Gitpod organizations that the connected account has access to. ### list_workspace_sessions Provides a log showing when specific workspaces were started or stopped in an organization. ### list_workspaces Shows a list of all currently defined workspaces within the connected organization. ### start_workspace Activates and starts up an existing, pre-defined workspace for immediate use. ### stop_workspace Pauses a running workspace, stopping its compute resources to save money. ### update_configuration Modifies the rules or settings for an existing repository configuration. ### update_organization_member Changes a user's role or permissions within the organization structure. ### update_organization_settings Modifies core operational settings for the entire Gitpod organization. ## Prompt Examples **Prompt:** ``` List all my Gitpod organizations. ``` **Response:** ``` I've found 2 organizations: 'Engineering-Team' (ID: org_123) and 'Open-Source-Projects' (ID: org_456). Which one would you like to explore? ``` **Prompt:** ``` Create and start a workspace for https://github.com/gitpod-io/gitpod. ``` **Response:** ``` Starting the `create_and_start_workspace` action... I've successfully triggered a new workspace for that repository. You can now access your cloud IDE. ``` **Prompt:** ``` Stop the workspace with ID 'ws-abc-123'. ``` **Response:** ``` I am stopping the workspace 'ws-abc-123' now. The environment will be hibernated to save resources. ``` ## Capabilities ### Provisioning and managing workspaces Start new development environments from repository URLs or delete existing ones when they are no longer needed. ### Organization governance Manage team access by creating organizations, listing members, adding users, or removing them completely. ### Configuration management Define and update repository-specific settings and environment variables to ensure consistent dev setups across all team members. ### Monitoring and auditing Track usage by listing workspace sessions, checking audit logs, or reviewing current organization details. ## Use Cases ### Onboarding a new developer to a complex service A new hire asks the agent to get started. The agent uses `create_organization` if needed, then runs `list_configurations` to find the correct project settings, and finally uses `create_and_start_workspace` to hand them a ready-to-go dev environment in seconds. ### Reviewing access rights before an audit The security lead asks for confirmation of who can deploy. The agent runs `list_organization_members`, checks the results with `get_organization_settings`, and then sends a summary report, eliminating manual database lookups. ### Reproducing bugs from production code A tester reports an issue linked to specific environment variables. Instead of asking the team to manually set up the build, the agent uses `get_configuration` and then `create_environment_variable` with the necessary values to recreate the bug locally. ### Decommissioning a retired project The manager knows Project Phoenix is finished. The agent first runs `list_workspaces`, confirms all environments are stopped, and then uses `delete_organization` to wipe clean the entire project footprint. ## Benefits - Stop clicking through multiple dashboards. You can now initiate a workspace directly via your agent, using the `create_and_start_workspace` tool to spin up an environment for any PR link instantly. - Never forget who has access. Use the listing tools—like `list_organization_members` and `get_organization_settings`—to manage team roles and ensure compliance without logging into a separate admin panel. - Maintain perfect consistency across projects by managing variables programmatically. You can use `create_environment_variable` to inject required keys, ensuring every developer starts with the exact same setup. - Save time and money on orphaned resources. When a feature is done, trigger the agent to run `delete_workspace` or `stop_workspace` instead of manually tracking down running machines. - Audit your team's activity easily. The `list_audit_logs` tool gives you an immediate view of resource usage across all teams, which is critical for cost management and security reviews. ## How It Works The bottom line is your agent manages cloud development resources using simple instructions instead of requiring complex API calls. 1. First, subscribe to this MCP in Vinkius and provide your Gitpod Personal Access Token. 2. Next, issue a natural language command through any compatible AI client—for instance, 'Start a dev environment for the main branch of my repo.' 3. Your agent executes the necessary tools, creating the workspace or updating the configuration, and you get immediate confirmation that the task is done. ## Frequently Asked Questions **How do I use Gitpod MCP to start a development environment?** You initiate this by telling your agent what repository URL you need. The agent then calls `create_and_start_workspace` and provides you with immediate access to the live cloud IDE. **Can Gitpod MCP help me manage team roles?** Yes, it manages membership using tools like `list_organization_members` and `update_organization_member`. This lets you change a user's access level instantly via command. **What is the best way to audit workspace usage with Gitpod MCP?** You use the `list_audit_logs` tool (if available for your account). It gives you a comprehensive history of actions, which is essential for tracking resource consumption. **Does Gitpod MCP allow me to delete an entire organization?** Yes. If a project is completely finished and decommissioned, the agent can run `delete_organization`, ensuring all associated resources are cleaned up. **How do I update environment variables using Gitpod MCP?** You simply ask your agent to add or change an environment variable. It calls `create_environment_variable` and ensures the setting is applied correctly to the target configuration.