Provider REST API

18 actions

Connect Claude to Easypanel

Inspect, deploy, start, stop and read the logs and metrics of projects and services on your own Easypanel server. Toolspoke puts 18 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: User API key
Actions exposed: 18
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Easypanel
Open the marketplace in your workspace, add Easypanel to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with user api key. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Easypanel shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Easypanel asks for

User API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

Easypanel URLRequired: The address you open Easypanel at. It has to be publicly reachable over HTTPS - a private-network address is refused.; https://panel.example.com
API keyRequired: Easypanel → Settings → Server → Users → Generate API Key for the user this connection should act as. It has that user's project access; a non-admin user only reaches the projects it was granted.

What Claude can do in Easypanel

18 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 11Reads
Writes: 5Writes
Destructive: 2Destructive

Reads

Fetches data and changes nothing.

list_projects
List the projects this key's user can access. Takes no arguments, which is why an install tests itself with it; project names are what every other call takes.
list_projects_and_services
List every accessible project together with its services and their types (app, compose, databases and so on). The quickest way to find a service name.
inspect_project
Read one project with its services and resolved domains.
inspect_app_service
Read an app service's full configuration and deployment state - source, build, domains, resources and environment variables. The environment usually holds secrets, so this response is never written to the audit log.
inspect_compose_service
Read a Docker Compose service's configuration and deployment state, including its environment. Never written to the audit log, for the same reason as inspect_app_service.
get_service_error
Read the latest startup error a service reported. The first thing to check when a service will not come up.
query_service_logs
Read a service's log lines from the panel's log store, optionally filtered by text, level, stream or time range. Requires log aggregation to be enabled on the panel. Log lines can hold user data, so they are not written to the audit log.
get_service_metrics
Read a service's CPU, memory, network and disk usage over time.
list_actions
List recent actions - builds, deployments, starts, stops, env changes - optionally for one project or service. Use the id with get_action to read a build log.
get_action
Read one action with its execution log - the build or deploy output. Logs can echo build-time secrets, so this is not written to the audit log.
list_domains
List the domain mappings this user can see, optionally for one service.

Writes

Creates or updates something on the other side.

deploy_app_service
Build and deploy an app service from its configured source. The service restarts on the new build. Watch progress with list_actions.
deploy_compose_service
Build and deploy a Docker Compose service from its configured source.
restart_app_service
Restart an app service without rebuilding it.
start_app_service
Enable and start a stopped app service, without rebuilding it.
stop_app_service
Stop and disable an app service. It goes offline until start_app_service is called, but nothing is lost, so it is a write rather than destructive.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

update_app_env
Replace an app service's entire environment with the given .env text. Destructive, not a write: every variable not in the new text is gone, the old values cannot be read back afterwards, and the service picks the change up on its next deploy. Read the current env with inspect_app_service first and send the whole set.
destroy_app_service
Permanently delete an app service with its files, domains, backups and image. There is no undo.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 18 actions above are the whole of it. A call to any other name is refused before it reaches Easypanel rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to Easypanel of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Easypanel: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Easypanel. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Easypanel's own rate limits. A call that Easypanel refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Easypanel?

18 named actions: 11 that only read, 5 that write and 2 that delete or permanently alter something. They include list_projects, list_projects_and_services and inspect_project. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Easypanel connector need?

User API key. The connector asks for easypanel url and api key. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Easypanel connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 18 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Easypanel connector not do?

The 18 actions above are the whole of it. A call to any other name is refused before it reaches Easypanel rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Easypanel of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Easypanel. An agent has to ask. Toolspoke does not retry, queue or back off around Easypanel's own rate limits. A call that Easypanel refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Easypanel's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Easypanel?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More infrastructure connectors

Browse all of them