Before any workflow starts, it helps to know your system is alive. Running a test connection gives you immediate confirmation that Guepard MCP is reachable and ready. This quick check prevents wasted runs, failed automations, or confusing errors. It is a small action that gives you confidence to move forward without hesitation.

Every environment you own, from production to sandboxes, can be seen in one snapshot. Listing deployments gives you an overview of what exists, what is running, and where you need to act. It is your control panel for the environments under your account, helping you make quick, informed decisions.

Sometimes you need more than a headline view. Get deployment shows you the full picture of a single environment, including compute profiles, branches, and recent snapshots. This level of detail helps you understand how it is set up and what state it is in before you make changes.

Launching a new environment should not take hours. With create deployment, you can start fresh in seconds by choosing an image, selecting a performance profile, and optionally seeding from a snapshot. It is the easiest way to set up test environments, staging systems, or even new production deployments without friction.

Before you run jobs, check the state of your compute. This tool tells you whether it is stopped, starting, or running so you always know what is available. Having this visibility prevents wasted effort and helps you time your work more effectively.

Bring your environment online with a single command. Start compute powers up the resources you need for testing, workloads, or live systems. You get the flexibility to activate environments on demand, then shut them down when you are done.

When the work is complete, stop compute gracefully shuts down resources. Your environment stays intact while costs are reduced and resources are freed. It is an easy way to keep things tidy and efficient without losing progress.

Every deployment has a history. Listing snapshots shows you every saved state across all branches, letting you trace progress or roll back if needed. It is your complete timeline of changes at the environment level.

Fork your database from any snapshot, test features or new migrations safely without touching production.
Branching allows you to spin up instant clones without duplicating data and enables agents to work in parallel with 0 risks.

Take a snapshot any time you want to freeze your work in place. Whether before a migration, after a release, or in the middle of an experiment, snapshots create a safety net. You gain freedom to explore knowing you can always return to a stable state.

Just like with Git, your database can have multiple lines of work. Listing branches shows you everything that exists, which ones are active, and how they diverge. It helps teams coordinate and makes data work as collaborative as code.

Branching lets you create a safe playground from any snapshot. You can try new features, test migrations, or experiment without risking production data. Instant cloning with zero data duplication keeps it fast and lightweight.

Switching between environments should be seamless. Checkout branch moves your active context to any branch, letting you work in dev, staging, or production without rebuilding. It keeps your workflow smooth and adaptable.

Sometimes you need to go back in time. Checkout snapshot lets you activate a specific saved state, perfect for debugging, audits, or reproducing issues. You can explore past data without changing the future of your environment.

Different jobs need different power. Listing performance profiles shows you the available options, from lightweight development setups to high performance production engines. You can compare them side by side and pick the right one for your workload.

Every deployment begins with a foundation. Listing image providers gives you access to supported engines and versions, from Postgres releases to specialized database stacks. You can select the right base image for your project and build on top of it with confidence.

Subscribing to a deployment turns it into a live channel of information. You receive updates the moment branches are created, snapshots are captured, or compute changes state. Instead of guessing or refreshing, your agents and dashboards stay synchronized automatically. This keeps everyone aligned and allows your workflows to react instantly to change.

Once a project is complete or an environment is no longer relevant, you can easily stop following its updates. Unsubscribing silences that feed, keeping your workspace clear of distractions. It is a simple way to stay focused on active work while avoiding unnecessary noise from deployments that no longer matter.

When you are tracking many deployments, it is easy to lose track of your feeds. Listing subscriptions gives you a full overview of what you are following, where events are coming from, and what is still relevant. This clarity helps you audit, clean up, or adjust your event streams whenever needed.

Scaling means handling more than one feed at a time. With manage subscriptions you can add, pause, or remove multiple feeds in bulk, saving hours of manual adjustments. It is the fastest way to adapt your event flow as priorities shift and projects evolve.