Cloudpress MCP

Live

OAUTH 2.0

DEVELOPER TOOLS

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...

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Cloudpress MCP
agent · Acme Q3
Run
Activate Shield in Cloudpress MCP
cloudpressmcp_activate_shield
85ms
Message Claude...

Cloudpress MCP tools for AI agents

CALL ANY TOOL
12 tools covering check, activate, create.
cloudpressmcp_activate_shield
Activate shield (waf/security) for a cloudpress site.
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
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.
1
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
2
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
3
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
4
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
DevOps assistant agent
Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs by feature, fix, or chore and publish release notes per tag. No manual changelog grooming.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought.
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.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""cloudpressmcp"": {
""url"": ""https://mcp.scalekit.com/cloudpressmcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.cloudpressmcp]
url = ""https://mcp.scalekit.com/cloudpressmcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""cloudpressmcp"": {
""url"": ""https://mcp.scalekit.com/cloudpressmcp"",
""type"": ""http""
}
}
}