Other · Remote MCP server
Puppetflow
Build, run, monitor, and control Puppetflow browser automations from AI clients.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.puppetflow/mcp- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-31
- Updated
- 2026-08-31
- Publisher
- com.puppetflow
- Namespace
- Namespace verified by the MCP Registry via the domain puppetflow.com · how
- Listed under
- Browser automation MCP servers
- Website
- docs.puppetflow.com/guide/mcp
- Repository
- github.com/puppetflow/puppetflow
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://{instance_host}/api/workspaces/{workspace}/mcp-server/http | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect Puppetflow
Puppetflow is a remote MCP server: there is nothing to install. Its endpoint is https://{instance_host}/api/workspaces/{workspace}/mcp-server/http, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {instance_host} and {workspace}.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Pulse MCPFree, agent-first social-post metrics - a post URL in, views/likes/comments out. | Local · stdio |
| Pulse SubregistryMCP server providing access to the PulseMCP Sub-Registry for browsing and discovering MCP servers. | Local · stdio |
| PulseGateIdentifiers PulseGate holds for a software project, and where each one came from. | Remote · HTTPLive check: ✓ handshake |
| Pumperly MCPMCP server for Pumperly - query fuel prices, find stations, and plan routes. | Local · stdio |
| purchaseiq.ioPre-purchase trust checks for AI agents: recalls, scam signals, proceed/caution/avoid verdict. | Remote · HTTPLive check: ✓ handshake |
| PursersCoordinate AI-agent work on a local-first, owner-controlled MCP board. | Local · HTTP, stdio |
| PusharyThe decision layer for AI agents. Your agent asks, a person approves or denies on their phone. | Remote · HTTP, SSELive check: ✓ handshake |
| Pusher ChannelsTrigger events, query channels, and manage realtime messaging on Pusher Channels. | Local · stdio |