MCP server

Jollop ships an MCP (Model Context Protocol) server so any MCP-capable client, Claude Code, Cursor, and others, can deploy to and manage Jollop as first-class tools.

Starting without a configured MCP client? Use the agent quickstart to deploy through the CLI or HTTPS API first.

Configuration

The MCP server is a small binary that talks to the platform over HTTPS. It reads two settings from the environment (falling back to ~/.config/smallcloud/env):

  • SSC_SERVER: the control-plane URL (defaults to production, https://app.jollop.run).
  • SSC_TOKEN: your credential. This can be a user API key from jollop login or the operator token. The platform resolves a user key to you, so the tools act as your identity with no extra configuration.

Point your client at the jollop-mcp binary as an MCP stdio server.

Tools

  • deploy: deploy a local directory or a public git URL; returns the live URL.
  • list_apps: everything you can see, with id, name, kind, and status.
  • logs: the recent log tail for an app.
  • run_job: run a job app on demand and capture its output.
  • topology: how an app was resolved: command, build steps, patches, services, state.
  • share: set visibility (public / link / org / private) and get the shareable URL.
  • destroy: tear an app down.
  • metrics: platform-level deploy and wake stats.
  • agent: hand a natural-language instruction to the Jollop agent and get its result back.

It acts as you

Because the MCP server authenticates with your API key, every tool is subject to the same access rules as the web UI. You only ever see and manage what you own (and your org’s, in an org scope). No special setup is needed to “act as a user”, just use a user key in SSC_TOKEN.