for agents & developers

Connect your agent to MoltsHost.

One MCP server. One project key. After that the agent can deploy, read logs, add domains, set secrets and roll back. A REST API is there if your client does not speak MCP.

get a project key how it works

connect

Add the MCP server.

Server URL: https://mcp.moltshost.com. Auth: your project key as a bearer token.

claude codeone line

$ claude mcp add moltshost https://mcp.moltshost.com \
    --header "Authorization: Bearer mh_your_project_key"

cursor and other mcp clientsmcp config json

{
  "mcpServers": {
    "moltshost": {
      "url": "https://mcp.moltshost.com",
      "headers": {
        "Authorization": "Bearer mh_your_project_key"
      }
    }
  }
}

Replace mh_your_project_key with the key for your project. The config file location depends on your client.

setup

Three steps, once per project.

/ 01

Human signs up

Pick a plan and start the 3-day trial. The human pays. The agent never needs the account login.

/ 02

Create a project key

One key for one project. It starts with mh_.

/ 03

Add the server

Use the command or the JSON above. Then ask the agent to deploy.

tools | preview

What the agent can call.

Preview. Names may change before launch. Your MCP client lists the real tools when it connects. Trust that list over this page.

deployPublish the project. Upload, build and put it online.

statusCheck the project. See if it is live and what the last deploy did.

logsRead logs. Find out why a build or a request failed.

domains.addAttach a domain. SSL is issued automatically.

env.setSet an env secret. Stored encrypted.

rollbackGo back. Put the previous version online again.

Request and response formats are not published yet.

what you can deploy

Sites and apps, same key.

Sites

Static, PHP and WordPress, with MySQL. Own domain, free SSL and CDN. Site plan and up.

staticPHPWordPressMySQL

Apps

Node, Python and Docker. Each app in its own micro VM. PostgreSQL included. Idle apps sleep and wake on the first request. App plan and up.

NodePythonDockerPostgreSQL

rest api

No MCP? Use HTTP.

The REST API does the same jobs as the MCP server and uses the same project key. Use it from CI, scripts or any agent that can make an HTTP request.

okSame key. The project key that works over MCP works over REST.

okSame scope. One key reaches one project, whichever way you call.

The API reference is not published yet. It will be linked here at launch.

key scoping

One key, one project.

An agent with a key can only touch the project that key belongs to.

okProject scoped. Every API key belongs to exactly one project.

okNo master key. There is no key that can do everything.

okTwo projects, two keys. Create a separate key for each project.

okSecrets encrypted. Env secrets are never stored as plain text.

okIsolated apps. Each app runs in its own micro VM.

okBackups out of reach. Kept in a separate account, cannot be deleted.

If you are a developer

Keep the key in your MCP client config, not in the repo
Give each agent the key for the project it works on, nothing more
Pass app credentials with env secrets, not in source files

If you are an agent

Ask your human for a project key. Do not ask for the account password
Do not write the key into code, commits or logs
If a call is refused for another project, ask for that project's key

SYS: WAITING FOR KEY

Get a key. Say "deploy".

3 days free. From $1 a month after that.

start 3-day free trial