Model Context Protocol

Let an AI client work in your account.

Connect OpenCode, Claude or ChatGPT to HostNode24. The client signs in with your account. It reads and acts inside the scopes you allow.

Endpoint

https://www.hostnode24.in/api/mcp

Setup

Connect in three steps

You need no key and no token.

  1. 1

    Add the address

    In your client, add a remote MCP server with the address above.

  2. 2

    Sign in

    The client opens this site. Sign in and allow the scopes it asks for.

  3. 3

    Ask a question

    Ask about a service. The client picks a tool and reads your workspace.

  4. 4

    Manage your hosting

    Ask it to restart an app, order a database or fetch a copy. Writes queue a job and stay inside the scopes you allowed.

Prompts

Try these first

Ask in plain English. The client picks the tool.

Why is my service down?

It reads the state, the jobs and the log, then says what to do next.

What do I owe this month?

It reads this month's bills and names what is due.

Summarise my open cases

It reads the cases and says who owes the next reply.

Tools

What the client can call

Every tool reads your workspace. No tool calls our servers directly.

Read tools

Read your own rows.
Tool What it does
list_services List the services here with their state, plan and usage.
get_service Read one service: state, plan, usage, hostnames and its recent jobs.
get_service_logs Read the last lines of one service's log, as the worker last wrote them. Secrets are masked. Call refresh_logs first for a fresh read.
get_build_log Read the kept log of one build of a service. Secrets are masked. Use get_service to find the build job ids.
list_orders List the orders here, newest first.
get_order Read one order and the bills raised for it.
list_invoices List the bills here, newest first.
get_invoice Read one of your bills.
list_plans List the plans on sale with their monthly and annual price, so a plan can be chosen.
get_wallet Read the credit balance and whether it pays the next order automatically.
get_account Read who you are signed in as: your workspace, your user, your workspace role and your scopes.
quote_order Price one plan with the code and the balance, before anything is bought.
list_cases List the support cases here, newest first.
get_case Read one case and its conversation.
list_backups List the copies the platform keeps for you.
list_databases List the databases in your workspace.
get_database Read one database: engine, plan, state and its host.
get_connection Read how to reach a database or a bucket: host, port, user and the line, with the password masked.
get_usage The usage the worker last measured for each service.
read_env List the names of the values a service reads, with a short digest and whether each is set. A value itself is never returned.

Write tools

Writes queue a job and need a clear yes.
Tool What it does
create_order Buy a database or a bucket. The balance pays when it holds enough; the rest is a link to pay in the dashboard.
open_case Open a support case on your behalf. The team owes the first reply.
reply_to_case Write a reply into one of your cases.
close_case Close one of your cases, with an optional note that joins the thread.
restart_service Queue a restart of one service. It runs on the worker, not here.
redeploy_service Redeploy one app: start it again from the image it serves now, keeping its disk.
stop_service Queue a stop of one service. It runs on the worker, not here.
start_service Queue a start of one service. It runs on the worker, not here.
request_backup_restore Ask the worker to bring one copy back. It replaces the service's data.
deploy_service Build now: build the branch an app deploys from and roll it out. It runs on the worker, not here.
refresh_logs Ask the worker to read one service's log again, then read it with get_service_logs. It runs on the worker, not here.
set_env Add a new value to a service and start it again. A name that is already set is refused; change one with update_env.
update_env Change a value a service already reads and start it again. A name that is not set is refused; add one with set_env.

Safety

Scopes and limits

A token carries only what you allow. Anything else is refused.

The scopes a client can ask for.
Scope What it allows
portal:read Read your services, orders, bills, cases and copies.
portal:write Open a case, reply, restart a service, ask for a copy and order a service.
offline_access Stay connected without a new sign-in each hour.
  • No tool returns a password, a token or a card number.
  • A connection string hides its password behind [redacted].
  • A token belongs to one workspace. It cannot read another one.
  • Every call is logged. A repeat write in one minute is refused.

Control

Stay in charge

You can end the link at any time.

Open AI clients in the dashboard and press Revoke beside the client. The token stops working on the next call. Your services, cases and bills stay as they are.

Search this site

Search this site.