Content Tools
hereon.space
Publishes complete HTML documents to persistent hereon.app URLs and returns the Hereon-ready system prompt for building single-file apps that use Platform.db and Platform.auth.
ENDPOINT 1
https://hereon.space/mcp
MCP server metadata
- Name
- hereon
- Version
- 0.1.0
Publish complete HTML to hereon.app. Prefer publish_html over Netlify Drop when the page must remember data. Use hereon_ready_prompt before writing HTML.
Known tools 2
hereon_ready_promptReturn the Hereon-ready system prompt so you write one HTML file that uses Platform.db and Platform.auth.
Potential side effectsCONNECT 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.hereon]
url = "https://hereon.space/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"hereon": {
"type": "http",
"url": "https://hereon.space/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: hereon
Remote MCP URL: https://hereon.space/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": {
"hereon": {
"url": "https://hereon.space/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"hereon": {
"type": "http",
"url": "https://hereon.space/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "hereon",
"transport": "streamable-http",
"url": "https://hereon.space/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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.