Bring Cloud Ide
to Cursor
Learn how to connect Gitpod to Cursor and start using 26 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 Cursor?
Cursor's Agent mode turns Gitpod into an in-editor superpower. Ask Cursor to generate code using live data from Gitpod and it fetches, processes, and writes. all in a single agentic loop. 26 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Gitpod in Cursor
Gitpod and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Gitpod to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
AgroLog
11 toolsAccess grain monitoring data via AgroLog — monitor temperature, moisture, CO2, crop levels, weather, and control aeration systems from any AI agent.
CData Connect Cloud
8 toolsUniversal Data Gateway mapping explicitly proxy structures parsing SQL schemas dynamically connecting APIs natively.
Marketplacer (Enterprise Marketplace Platform)
9 toolsManage your enterprise marketplace via Marketplacer — list products, track orders, and audit seller networks.
Regex Toolkit
3 toolsEquip your AI with strict Regular Expressions. Deterministically extract, validate, and redact Emails, URLs, and Phones without hallucinations.