← Registry

Developer Tools

websitestarter.org

Guides users through a Website Starter workflow and generates customized instruction-only starter ZIPs.

1 endpoint4 known toolsFirst detected September 14, 2026Last detected September 14, 2026

ENDPOINT 1

https://websitestarter.org/mcp

No auth detected

MCP server metadata

Name
website-starter
Version
2.0.0
Capabilities
tools.listChanged

Known tools 4

start_website

Start the guided Website Starter workflow.

Inferred read-only
describe_starter

Describe the Website Starter instruction set, its current version, public download, and safety boundaries.

Inferred read-only
get_starter

Return a direct public link to the current neutral instruction-only Website Starter ZIP.

Inferred read-only
create_starter

Create a customized instruction-only Website Starter ZIP after the start_website interview.

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.website-starter]
url = "https://websitestarter.org/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "website-starter": {
      "type": "http",
      "url": "https://websitestarter.org/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: website-starter
Remote MCP URL: https://websitestarter.org/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": {
    "website-starter": {
      "url": "https://websitestarter.org/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "website-starter": {
      "type": "http",
      "url": "https://websitestarter.org/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "website-starter",
  "transport": "streamable-http",
  "url": "https://websitestarter.org/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.