Skip to content

AI assistants (MCP)

Netkeel speaks the Model Context Protocol (MCP), so an AI assistant that supports it can work with your account. It can answer questions such as “which applications have an update waiting?” or “what does the PHP error log say?”, and, if you allow it, take a backup or restart PHP for you.

By default an assistant can only look. Nothing it does can change your account until the owner turns on Allow tokens to make changes and gives a token the Read and change permission. Even then, changes that take applications offline, cannot be undone, run your own commands or cost money only run after the assistant has shown you what would happen and you have agreed (see Changes that need your agreement). An assistant never sees passwords, keys or database credentials.

Only the account owner and super admins can create tokens and turn changes on.

  1. In the sidebar, open Integrations, then API & MCP.
  2. Click Create token.
  3. Give it a Name, such as “Claude Code on my laptop”.
  4. Under What it can do, keep Read only, or choose Read and change (see Let an assistant make changes).
  5. Choose when it Expires: 30 days, 90 days or 1 year. A Read only token can also have no expiry. A Read and change token always expires, after a year at most.
  6. Enter Your password. If you have two-factor authentication on, enter an Authenticator code too.
  7. Click Create token.
  8. Copy the token now. It starts with nkm_ and is shown only once.

The page shows the address to use under MCP server, for example https://my.netkeel.com/api/mcp, and a ready-made setup with your new token filled in.

Every client needs the same two things: the MCP server address, and an Authorization header with Bearer and your token. In the examples below, replace https://my.netkeel.com/api/mcp with the address shown on the page, and nkm_YOUR_TOKEN with your token.

Run this in a terminal:

Terminal window
claude mcp add --transport http netkeel https://my.netkeel.com/api/mcp --header "Authorization: Bearer nkm_YOUR_TOKEN"

Add --scope user before netkeel to use Netkeel in every project, not only the current one. Run claude mcp list to check that it connected.

Claude Desktop’s configuration file starts local programs only, so it reaches Netkeel through a small bridge, mcp-remote, that runs with npx. You need Node.js 18 or later.

  1. In Claude Desktop, open Settings, then Developer, and click Edit Config. This opens claude_desktop_config.json.

  2. Add Netkeel under mcpServers:

    {
    "mcpServers": {
    "netkeel": {
    "command": "npx",
    "args": ["-y", "mcp-remote", "https://my.netkeel.com/api/mcp", "--header", "Authorization:${NETKEEL_AUTH}"],
    "env": { "NETKEEL_AUTH": "Bearer nkm_YOUR_TOKEN" }
    }
    }
    }

    Keep Authorization:${NETKEEL_AUTH} exactly as it is, with no space: the token goes in env. A space inside args breaks the command on Windows.

  3. Save the file and restart Claude Desktop.

Add this to ~/.cursor/mcp.json to use Netkeel in every project, or to .cursor/mcp.json in one project:

{
"mcpServers": {
"netkeel": {
"url": "https://my.netkeel.com/api/mcp",
"headers": { "Authorization": "Bearer nkm_YOUR_TOKEN" }
}
}
}

Add this to .vscode/mcp.json in your project:

{
"servers": {
"netkeel": {
"type": "http",
"url": "https://my.netkeel.com/api/mcp",
"headers": { "Authorization": "Bearer nkm_YOUR_TOKEN" }
}
}
}

Any client that supports remote MCP servers over HTTP with a custom header works: give it the address and the Authorization: Bearer header. The connection uses plain HTTP POST requests (the “streamable HTTP” transport of MCP). A client that can only start local programs can use the mcp-remote bridge, as Claude Desktop does.

Changes are off until you turn them on. Two things must both be true before an assistant can change anything:

  1. Allow tokens to make changes is on for the account.
  2. The token was made with Read and change.

To turn changes on:

  1. In the sidebar, open Integrations, then API & MCP.
  2. Switch on Allow tokens to make changes.
  3. Enter Your password, and an Authenticator code if you have two-factor authentication on, then confirm.
  4. Create a token and choose Read and change. (This choice is greyed out while the switch is off.)

To go back to read-only, switch Allow tokens to make changes off. Every token becomes read-only straight away and you do not have to revoke any. Turning it off needs no password.

Every change is recorded in your account’s Activity under the token’s name, for example AI assistant "Claude Code on my laptop".

Some changes never run on the assistant’s first try:

  • They take applications offline for a while: rebooting a server, restarting its services, disabling or enabling an application, deploying from Git, and switching the PHP version.
  • They cannot be undone, or they run your own commands: deleting an application, a server or a backup, restoring a backup, putting staging live (or live over staging), and adding a cron job or a redirect.
  • They cost money: ordering a server and installing an application.

For these the assistant first gets a preview, “DRY RUN: nothing was changed”, that says what would happen and holds a confirmation code. It is told to ask you, and to send the change again with the code only after you agree. The code works once, for 10 minutes, and only for exactly that change. If the assistant never asks, nothing is changed.

Your usual limits still apply to everything an assistant does: your plan, your server limits and your spending budget.

With Read only, an assistant can:

Tool What it returns
list_servers, get_server Your servers with their name, location, size, status, whether the Netkeel agent on each is online, resource use and the applications each hosts.
get_server_uptime A server’s uptime and outages over 7, 30 or 90 days.
get_server_firewall Whether the firewall is on, its rules, blocked addresses and recent blocked attempts.
list_server_options The providers, locations, sizes and prices you can order, and whether you may order a server now.
list_applications, get_application Your applications: domain, type, status, environment, PHP or Node.js version, the server each runs on and whether an update is available.
get_application_logs The latest lines of one log of an application (source, max_lines up to 200). The sources are nginx-error (the default), nginx-access, php, cron, app (the output of Node.js, AI agent and Joomla applications), and laravel and queue for Laravel. See Application logs.
get_application_domains An application’s domains and whether their DNS points to the server.
get_application_settings PHP version and options, PHP limits, cache and Redis settings, cron jobs and redirects.
get_git_deploy An application’s Git deploy: repository, branch and recent deployments.
list_backups Your applications with their backups, or one application’s backups and schedule.
list_alerts, list_activity, list_jobs, get_job Open alerts, the activity log, background jobs, and the status of one job.
get_application_uptime Uptime monitoring of an application’s address.
get_usage_summary, get_spend_summary This month’s usage per server, and your budget, spend so far and forecast. Card details and invoices are not included.
list_notification_channels Your notification channels, their health and which alerts go where. Addresses and secrets are not included.

With Read and change, and Allow tokens to make changes on, it can also:

Tool What it does
create_backup Take a backup now.
restore_backup, delete_backup Restore a backup, or delete one. Needs your agreement.
set_php_version, purge_cache, restart_php Switch an application’s PHP version, clear its caches, restart its PHP.
add_cron_job, delete_cron_job Add or remove a scheduled command. The command is one line of up to 700 characters. Adding one needs your agreement.
add_redirect, delete_redirect Add or remove a 301 or 302 redirect. Adding one needs your agreement.
set_application_status Disable or enable an application. Needs your agreement.
deploy_application Start a Git deployment. Needs your agreement.
create_staging Create a staging copy. The staging password stays in the panel.
push_staging, pull_staging Put staging over live, or live over staging. Needs your agreement.
create_application Install an application on a server. Needs your agreement. The generated passwords stay in the panel.
delete_application Delete an application from its server. Needs your agreement.
reboot_server, restart_service Reboot a server, or restart one or all of its services. Needs your agreement.
create_server Order a server at the price list_server_options showed. Needs your agreement.
delete_server Delete a server. Needs your agreement, and is refused while the server still hosts applications.
dismiss_alert Dismiss an alert.

An assistant cannot change billing, payment methods, team members, your account or security settings, tokens, databases, files, SSH keys or the credentials of your integrations. Passwords, keys and tokens are left out of everything it receives.

Log text is handed to the assistant as data, inside <log-data> tags, and the tool tells the assistant it is not instructions. Results are cut at 50 KB.

Each token can make up to 120 requests, 60 tool calls and 20 changes a minute. Each account, over all its tokens, can make up to 150 tool calls and 40 changes a minute. These limits are shared with scripts that use the same tokens through the REST API. Over the request or call limit the assistant gets an error and has to wait a minute. Over the change limit it is told to wait a minute before it tries again.

The Access tokens table lists each token’s name, its first characters, what it can do (Read only or Read and change), when it was created, when it was last used and when it expires. An account can have up to 10 active tokens.

To stop an assistant, click Revoke next to its token and confirm. The assistant loses access straight away, and revoking cannot be undone: create a new token to connect again.

Use one token for each assistant or computer, so you can revoke one without affecting the others.

  • Read-only unless you say otherwise. Changes are off by default, and a token can only change things when both the account switch and the token allow it.
  • You decide the pace. Changes that take applications offline, cannot be undone, run your own commands or cost money only run after the assistant has shown a preview and you have agreed.
  • Shown once. Netkeel keeps only a fingerprint of the token, not the token. If you lose it, revoke it and create another.
  • One account. A token only reaches the account that made it.
  • Tied to its creator. A token works only while the person who made it is still an owner or super admin of the account. If that person is removed or demoted, the token stops working.
  • Not for browsers. Requests that come from a web page are refused. The endpoint only accepts a token in the Authorization header, never a login cookie.
  • Passwords never leave. Passwords, keys, tokens and database credentials are left out of everything the assistant receives.
  • Activity. Creating and revoking a token, turning changes on or off, and every change an assistant makes appear in your account’s activity, with the token’s name and never its value.

Treat a token like a password. Anyone who has it can do what it allows until you revoke it. Prefer Read only tokens unless an assistant really needs to make changes.