Skip to main content
Glama
gabrielchaves6

cloudfact

by gabrielchaves6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Expose a running app

expose
Idempotent

Publish a locally or SSH-reachable app to a public trycloudflare.com URL. Proxy HTTP and WebSocket traffic, keep it private by default or opt into a public link.

Instructions

Publish an app that is already listening on a port to a public *.trycloudflare.com URL (tunnel backend). Without ssh, the port is on this machine. With ssh (user@host), the app runs on another machine: cloudfact opens an SSH port-forward to it and publishes through here — nothing to install remotely (key-based SSH access required). HTTP and WebSocket traffic is proxied. Apps are PRIVATE by default (same #key gate as static deploys, with rate limiting and optional expiry); pass public=true to publish without the gate. Idempotent: the same port/host already live returns the existing URL (reused=true).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sshNoSSH destination of the machine running the app, e.g. ubuntu@10.0.0.5 or a Host alias from ~/.ssh/config
nameNoDeploy name (slug). Defaults to port-<port> or <host>-<port>
portYesPort the app listens on (locally, or on the SSH host)
publicNoPublish without the key gate (default false: private)
expiresNoPrivate key lifetime, e.g. "30m", "24h", "7d" (default: never expires)
restartNoRestart even if already live (yields a new URL)
sshPortNoSSH port (default 22)
identityNoPath to the SSH private key (default: ssh agent / ~/.ssh/config)
strictHostKeyNoRequire the SSH host key to be in known_hosts already (no first-connection trust)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the idempotentHint annotation, the description discloses concrete behavior: idempotent reuse with reused=true, key-based SSH requirements, private-by-default key gate, rate limiting, optional expiry, HTTP/WebSocket proxying, and restart behavior. This is rich, non-obvious behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence earns its place. The core purpose is front-loaded, followed by SSH mode, security defaults, and idempotency. No filler or redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 9 parameters, remote SSH behavior, security gates, and no output schema, the description covers the essential scenarios, prerequisites, defaults, and edge cases. An agent has enough context to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds meaningful parameter context: port location depends on ssh, public=true disables the gate, expires controls key lifetime, restart yields a new URL, and idempotency affects the result. This goes beyond the schema's individual field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Publish an app that is already listening on a port to a public *.trycloudflare.com URL.' This clearly identifies what the tool does and distinguishes it from deploy-style tools by emphasizing the app is already running.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use the tool: local ports vs remote ports via SSH, and it explains the SSH prerequisite. It does not explicitly name sibling alternatives or say when not to use it, but the 'already listening on a port' framing provides enough guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools