# ProAgentStore [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/ProAgentStore/platform  
**GitHub Stars:** 1  
**npm Downloads (last month):** 24114  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/proagentstore

## Description
MCP-first control plane for ProAgentStore agents and private instances.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "proagentstore": {
    "command": "npx",
    "args": ["-y","@proagentstore/cli"]
  }
}
```

## Documentation

## What ProAgentStore MCP server does

ProAgentStore exposes the ProAgentStore marketplace and agent control plane through Model Context Protocol. MCP clients can discover published agents, try a public agent without signing up, subscribe to an agent, inspect owned instances, add knowledge, and send messages to a private instance.

The platform supports three agent forms: conversational workers built from the `worker` template, scheduled workers built from `cron`, and stateless API tools built from `api`. A subscribed instance runs with its own state and knowledge. The instance runtime uses caller-provided Cloudflare Workers AI credentials rather than charging the platform's AI account.

## How it works

The hosted MCP endpoint is available at `https://mcp.proagentstore.online/mcp`. A typical workflow starts with `list_agents`, continues with `subscribe_agent`, then uses `my_instances`, `add_instance_knowledge`, and `chat_with_instance`. For quick discovery or smoke tests, `chat_with_agent` calls a public trial endpoint instead of creating a private instance.

Private runtime calls require the instance owner's Cloudflare Workers AI account ID and API token. If those credentials are absent, the runtime returns an instruction to add them before running the agent. This indicates that the private execution path is active while refusing to use the platform's credentials.

Browser- and coding-capable instances can also use the ProAgentStore local browser runtime. The `pags up` command serves active runtime-capable instances through an outbound WebSocket relay, with Playwright and terminal or coding capabilities available locally. Cloud-only agents without a runtime capability do not require that process.

## Setup and configuration

Connect an MCP client to the hosted endpoint using its streamable HTTP transport. Examples include:

- Codex: `codex mcp add proagentstore --url https://mcp.proagentstore.online/mcp`
- Claude Code: `claude mcp add --transport http proagentstore https://mcp.proagentstore.online/mcp`
- Generic proxy: `npx mcp-remote https://mcp.proagentstore.online/mcp`
- Local CLI proxy: `npx @proagentstore/cli mcp`

Codex and Claude Code may require an MCP login flow when the server reports that the client is not authenticated. The hosted service also provides OAuth scopes for `read`, `write`, `runtime`, and `destructive` operations. Set `MCP_READ_ONLY=1` to force read-only behavior where that configuration is available.

For local browser or coding execution, install the CLI with `npm i -g @proagentstore/cli`, sign in with `pags login`, and start the runner with `pags up`. Headless and device-based sign-in options are available for machines without a display.

## Tools and capabilities

- Discover published agents and call public trial chats.
- Subscribe to agents and list the caller's private instances.
- Add knowledge to an instance and chat with its runtime.
- Apply read, write, runtime, and destructive authorization scopes.
- Use dry-run options and exact confirmation values for applicable mutations.
- Review recent writes, runtime calls, dry runs, denied actions, and destructive events through `mcp_audit_log`.

## Limitations and notes

Private instance execution depends on user-supplied Cloudflare Workers AI credentials. The local runner is needed only for instances that declare runtime capability; cloud-only chat, retrieval, and connector agents are skipped by `pags up`. The runner connects outbound through a per-instance WebSocket relay and does not require an inbound port or tunnel. Live instance membership is polled every 20 seconds when using the default watched runner mode.

_Full upstream README: https://allmcps.com/mcp/proagentstore/readme_