Cloudpress MCP connector for AI agents

Cloudpress MCP tools for AI agents

CALL ANY TOOL

12 tools covering check, activate, create.

cloudpressmcp_list_sites

List sites

Returns all active sites in the Cloudpress account.

Parameters

Name

Type

Required

Description

—

No parameters required

cloudpressmcp_search_domains

Search domains

cloudpressmcp_list_orders

List orders

cloudpressmcp_get_site

Get site

cloudpressmcp_list_domains

List domains

cloudpressmcp_get_order

Get order

cloudpressmcp_list_subscriptions

List subscriptions

cloudpressmcp_get_domain

Get domain

cloudpressmcp_list_dns_zones

List dns zones

cloudpressmcp_get_subscription

Get subscription

cloudpressmcp_list_edge_rules

List edge rules

cloudpressmcp_get_cdn_logs

Get cdn logs

cloudpressmcp_list_site_tasks

List site tasks

cloudpressmcp_get_dns_zone

Get dns zone

cloudpressmcp_list_dns_records

List dns records

cloudpressmcp_get_cdn_status

Get cdn status

cloudpressmcp_list_rate_limits

List rate limits

cloudpressmcp_get_dns_record

Get dns record

cloudpressmcp_list_access_lists

List access lists

cloudpressmcp_get_waf_config

Get waf config

cloudpressmcp_list_domain_contacts

List domain contacts

cloudpressmcp_get_cdn_caching

Get cdn caching

cloudpressmcp_list_domain_registrations

List domain registrations

cloudpressmcp_get_cdn_metrics

Get cdn metrics

cloudpressmcp_list_waf_custom_rules

List waf custom rules

cloudpressmcp_get_dns_metrics

Get dns metrics

cloudpressmcp_list_waf_managed_rules

List waf managed rules

cloudpressmcp_get_origin_logs

Get origin logs

cloudpressmcp_list_curated_access_lists

List curated access lists

cloudpressmcp_get_cache_status

Get cache status

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="cloudpressmcp")

mcp = MultiServerMCPClient({
    "cloudpressmcp": {
        "url": "https://mcp.scalekit.com/cloudpressmcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

const token = await client.agent.getToken({ userId: "user_id", connector: "cloudpressmcp" });
// Connect to MCP at https://mcp.scalekit.com/cloudpressmcp

const token = await client.agent.getToken({ userId: "user_id", connector: "cloudpressmcp" });
// Connect to MCP at https://mcp.scalekit.com/cloudpressmcp

token = client.agent.get_token(user_id="user_id", connector="cloudpressmcp")
# Connect to MCP at https://mcp.scalekit.com/cloudpressmcp

Try these prompts

Paste any prompt into your agent to get started.

Update an existing custom WAF rule for a Cloudpress site?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Cloudpress MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Cloudpress MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Cloudpress MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Cloudpress MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

Engineering Teams

DevOps assistant agent

Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Engineering Teams

Auto release notes agent

Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. Scalekit resolves the real user credential.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Cloudpress as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Cloudpress OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Cloudpress?
Yes. Pass a tool name filter to listScopedTools so the DevOps agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Cloudpress.

What happens when a user revokes Cloudpress access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent change DNS or security rules on client sites?
Only sites in the authorizing user's Cloudpress account. DNS records, edge rules, and Shield changes attribute to that user, keeping agency client infrastructure auditable.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit