Compatible with every major AI agent and IDE
What is the Gitpod MCP Server?
Connect your Gitpod account to any AI agent to orchestrate your cloud development lifecycle through natural language.
What you can do
- Workspace Lifecycle — Create, start, stop, and delete workspaces using repository URLs or specific context IDs.
- Organization Management — List, create, and inspect organizations and their members to manage team access.
- Configuration & Env Vars — Manage workspace configurations and environment variables for consistent development setups.
- Audit & Sessions — Track workspace sessions and audit logs to monitor activity within your organizations.
How it works
- Subscribe to this server
- Enter your Gitpod Personal Access Token
- Start managing your cloud IDEs from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Developers — Spin up fresh dev environments for PRs or issues without leaving the chat or editor.
- DevOps Engineers — Automate organization settings and environment variable management across teams.
- Engineering Leads — Monitor workspace usage and audit logs to maintain security and cost efficiency.
Built-in capabilities (26)
Create and start a new Gitpod workspace
Create a new repository configuration in Gitpod
Create an environment variable for a repository configuration
Create a new Gitpod organization
Delete a repository configuration
Delete an environment variable
Delete a Gitpod organization
Delete a Gitpod workspace
Get details for a specific repository configuration
Get details for a specific Gitpod organization
Get settings for a Gitpod organization
Get details for a specific Gitpod workspace
Join a Gitpod organization using an invitation ID
List audit logs for an organization (Enterprise Only)
List repository configurations in an organization
List environment variables for a repository configuration
List members of a Gitpod organization
List all Gitpod organizations for the authenticated user
List workspace sessions (start/stop events) in an organization
List workspaces in an organization
Remove a member from a Gitpod organization
Start an existing Gitpod workspace
Stop a running Gitpod workspace
Update a repository configuration
Update a member role in a Gitpod organization
Update settings for a Gitpod organization
Why VS Code Copilot?
GitHub Copilot Agent mode brings Gitpod data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 26 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Gitpod in VS Code Copilot
Gitpod and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Gitpod to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Gitpod in VS Code Copilot
The Gitpod MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 26 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Gitpod for VS Code Copilot
Every tool call from VS Code Copilot to the Gitpod MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I create a workspace from a repo URL?
Yes! Use the create_and_start_workspace tool with the repository URL. Your agent will provision and start a cloud environment for that specific context immediately.
How do I see who is in my organization?
Simply ask the agent to run the list_organization_members action with your Organization ID. It will return a list of all users and their roles within that organization.
Can I manage environment variables for my development setups?
Yes. You can use create_environment_variable to set new secrets or configs, and list_environment_variables to review existing ones for your workspaces.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Rapid URL Indexer Alternative
5 toolsAutomate Google Search Console indexing — submit URL batches, track project progress, and manage credits directly via AI.

Hookdeck
52 toolsManage and monitor webhooks with Hookdeck — list connections, create sources, and control event routing directly from your AI agent.

Cloudflare Tunnel
17 toolsManage Cloudflare Tunnels directly from your AI agent — list, create, and configure secure Zero Trust connections to your private infrastructure.

Google Cloud Logging Stream
1 toolsThis MCP does exactly one thing: it queries logs using Google Cloud Logging. That's its only function, and nothing else. Incredible for giving your AI secure observability.
