Examples

CP-MCP works best when you ask for an outcome and let Claude work out the calls. These are patterns that reliably produce good results.

Inventory and orientation

List the authentication servers on my Cloudpath, and show the type of each.

Claude searches the API index for the relevant endpoint, calls it, and returns a table. You get the answer, not raw JSON.

How many registration lists are configured, and how many entries does each hold?

This needs pagination — Claude loops over ?page=N inside the sandbox and joins the results. See Calling conventions.

DPSK and passphrases

Create ten memorable three-word passphrases and add them to DPSK pool pool-guid.

Claude mints the passphrases with core.generate_passphrase and POSTs them into the pool in the same call, so the secrets never leave the isolate before Cloudpath has them.

Show me the DPSK pools and which policies they’re attached to.

Branded portal images

Generate a logo and favicon for the Harborview property portal — navy and gold, an aerial waterfront background — and upload both.

Claude renders the images with core.generate_image and uploads them through core.call in one invocation. Name your colors and the mood you want; the 4:1 banner crop is handled for you.

Property Management surface

Using property portal pmp-guid, list the properties and their management status.

Property Management calls are scoped to a portal GUID — name it (or the GUID) and Claude passes it as propertyMgmtPortalGuid. See The three API surfaces.

Tips

• Say which surface. “On the tenant portal…” or “on the property portal pmp-guid…” removes ambiguity when the same resource name exists on more than one surface.
• Ask for the evidence. “Show me the raw response” is always reasonable, and useful when a write didn’t take.
• Scope narrowly. A single code_mode invocation has a 20-second budget — one pool or one property at a time is faster than “audit everything”. See How code mode works.