PopKit MCP Server - exposes skills, agents, and commands as MCP tools
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"popkit-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# PopKit MCP Server Standalone MCP server that exposes PopKit skills, agents, and commands as MCP tools, resources, and prompts. Any MCP-compatible tool (Cursor, Codex CLI, Copilot, etc.) can connect to this server to use PopKit. ## MCP Tools | Tool | Description | | ------------------------- | ----------------------------------------- | | `popkit/run_skill` | Invoke any PopKit skill by name | | `popkit/spawn_agent` | Start an agent with a task | | `popkit/power_mode` | Legacy multi-agent compatibility workflow | | `popkit/create_handoff` | Build a coordination handoff packet | | `popkit/validate_handoff` | Validate a coordination handoff packet | | `popkit/get_context` | Retrieve project context | | `popkit/health_check` | System status and diagnostics | ## Usage The primary console script is `popkit-mcp`. The package also installs `popkit-mcp-server` as a longer compatibility alias. ```bash # stdio transport (default, for MCP clients) popkit-mcp # SSE transport popkit-mcp --transport sse --port 8080 # Streamable HTTP transport popkit-mcp --transport streamable-http --port 8080 ``` ## MCP Client Configuration Add to your tool's MCP configuration: ```json { "mcpServers": { "popkit": { "command": "popkit-mcp", "args": ["--transport", "stdio"] } } } ``` On Windows, `pip install popkit-mcp` may install `popkit-mcp.exe` in your user Scripts directory instead of on `PATH`: ```powershell %APPDATA%\Python\Python3xx\Scripts\ ``` Use `%APPDATA%` instead of copying another user's absolute path. Replace `Python3xx` with your installed Python folder. Run `python --version` to check the version. If you cannot edit `PATH`, configure your MCP client with the absolute path to `popkit-mcp.exe`: ```json { "mcpServers": { "popkit": { "command": "C:\\Users\\YOUR-USERNAME\\AppData\\Roaming\\Pyt…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.