DevOps

harvis.dev

A deployment tool that instantly publishes any local folder to a live URL via a single command, with an HTTP API and MCP server for agent integration.

1 endpoint1 known toolsFirst detected August 13, 2026Last detected August 15, 2026

ENDPOINT 1

https://harvis.dev/api/mcp

No auth detected

MCP server metadata

Name: harvis.dev
Version: 1.0.0

Capabilities

tools.listChanged

Known tools 1

deploy_site

Publish a static website to harvis.dev and get a live public URL back instantly.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.harvis-dev]
url = "https://harvis.dev/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "harvis-dev": {
      "type": "http",
      "url": "https://harvis.dev/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: harvis-dev
Remote MCP URL: https://harvis.dev/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "harvis-dev": {
      "url": "https://harvis.dev/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "harvis-dev": {
      "type": "http",
      "url": "https://harvis.dev/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "harvis-dev",
  "transport": "streamable-http",
  "url": "https://harvis.dev/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.