OAUTH 2.0
DEVELOPER TOOLS
Cloudpress is a managed WordPress hosting platform built for the AI era. Its MCP server lets AI agents manage sites, domains, DNS, security rules...
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/cloudpressmcpconst token = await client.agent.getToken({ userId: "user_id", connector: "cloudpressmcp" });
// Connect to MCP at https://mcp.scalekit.com/cloudpressmcptoken = client.agent.get_token(user_id="user_id", connector="cloudpressmcp")
# Connect to MCP at https://mcp.scalekit.com/cloudpressmcpDoes 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.