Skip to main content

Theo MCP

Theo's tools can be used by MCP-compatible clients through the CreeperPanel MCP endpoint:

https://ai.creeperpanel.com/mcp

This endpoint uses MCP Streamable HTTP. It is not a local stdio server, and you do not need to run a separate gateway or OpenAPI conversion tool.

info

Your MCP client must support Streamable HTTP and custom request headers.

What You Need​

Before connecting, create a CreeperPanel API key and secret for the server you want the client to access.

For help creating a key pair, see Authentication.

You will need:

  1. An MCP client that supports Streamable HTTP.
  2. Your CreeperPanel API key.
  3. Your CreeperPanel API secret.
  4. Any permissions needed for the actions you want the client to perform.

Connection Details​

Use the following MCP server URL:

https://ai.creeperpanel.com/mcp

Pass your credentials as headers on each MCP request:

x-api-key: {api-key}
x-api-secret: {api-secret}

Do not put your API key or secret inside MCP tool arguments. They are transport credentials, not tool inputs.

warning

Keep the secret private. If it is shared or exposed, revoke the key in CreeperPanel and create a new pair.

Adding The Server To A Client​

The exact setup screen depends on the MCP client you use, but the details are usually:

{
  "url": "https://ai.creeperpanel.com/mcp",
  "headers": {
    "x-api-key": "{api-key}",
    "x-api-secret": "{api-secret}"
  }
}

Once connected, the client should be able to list Theo tools from the MCP server.

If the client cannot send custom headers, it will not be able to connect directly to this endpoint.

Confirming Actions​

Some Theo tools only read information. Other tools can change server state, such as starting a service, installing a version, restoring a backup, or submitting a support ticket.

When a tool needs confirmation, the first call returns a confirmation_required result. The result includes a confirmation message and a confirmation id.

After you have reviewed the action, call the MCP tool confirm_action with:

{
  "confirmationId": "{confirmation-id}",
  "userMessage": "Yes, I confirm that action."
}

The confirmation is checked against the exact pending action stored by the server. If it matches, Theo runs that stored action. If it has expired, belongs to a different session, or the confirmation text does not match the action, it will be rejected.

What The Tools Can Do​

The MCP tools use the same Theo tool system as CreeperPanel:

  • read service, instance, file, backup, billing, support, and account context where permitted;
  • perform safe panel actions through the same backend paths used by Theo;
  • require explicit confirmation for mutating actions;
  • return structured results for clients that support them.

The tool list is generated from the live Theo tool registry, so available tools may change as Theo gains new supported actions.

Troubleshooting​

The Client Cannot Connect​

Check that the client is using https://ai.creeperpanel.com/mcp and supports Streamable HTTP. Older MCP clients may only support local stdio or legacy SSE servers.

Authentication Fails​

Check that both headers are present:

x-api-key: {api-key}
x-api-secret: {api-secret}

Also check that the key has not been revoked and belongs to the CreeperPanel server you want to manage.

A Tool Is Denied​

The API key may not have permission for that action, or the action may not be exposed through Theo. Adjust the key permissions in CreeperPanel, or complete the action directly in the panel.

A Confirmation Fails​

Confirmations are short-lived and tied to the authenticated session. Run the original tool again to get a fresh confirmation id, then call confirm_action with the new id and clear confirmation text.

Wiki offerGet 10% off