Defang

Created By
DefangLabs9 months ago
The Defang Model Context Protocol (MCP)⁠ Server is tailored for developers who work primarily within integrated development environments (IDEs). It enables seamless cloud deployment from supported editors such as Cursor, Windsurf, VS Code, VS Code Insiders, and Claude, delivering a fully integrated experience without leaving your development environment.
Overview

what is Defang?

Defang is a Model Context Protocol (MCP) Server designed for developers working within integrated development environments (IDEs). It facilitates seamless cloud deployment from supported editors like Cursor, Windsurf, VS Code, and Claude, providing a fully integrated experience without leaving the development environment.

how to use Defang?

To use Defang, developers can deploy their projects directly from their IDEs by utilizing the provided tools such as deploy, destroy, and estimate. The command to start the server is npx -y defang@latest mcp serve.

key features of Defang?

  • Seamless cloud deployment from various IDEs.
  • Tools for deploying, destroying, and estimating project costs.
  • Integration with popular cloud providers like AWS and GCP.

use cases of Defang?

  1. Deploying applications directly from an IDE to the cloud.
  2. Estimating costs for cloud deployments based on different configurations.
  3. Managing project configurations and services efficiently.

FAQ from Defang?

  • What IDEs are supported by Defang?

Defang supports Cursor, Windsurf, VS Code, VS Code Insiders, and Claude.

  • Is there a cost associated with using Defang?

Defang is free to use, but cloud deployment costs will depend on the chosen cloud provider.

  • Can I use Defang for any type of project?

Yes, Defang can be used for various types of projects that require cloud deployment.

Server Config

{
  "mcpServers": {
    "defang": {
      "command": "npx",
      "args": [
        "-y",
        "defang@latest",
        "mcp",
        "serve"
      ]
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
DefangLabs
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago