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.
# 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:
{
"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:
%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:
{
"mcpServers": {
"popkit": {
"command": "C:\\Users\\YOUR-USERNAME\\AppData\\Roaming\\Python\\Python313\\Scripts\\popkit-mcp.exe",
"args": ["--transport", "stdio"]
}
}
}
Replace YOUR-USERNAME with your Windows username and Python313 with your installed Python version. Run python --version to check the version.
Requirements
- Python 3.11+
mcpSDK (^1.12.0)popkit-shared(installed automatically bypip install popkit-mcp)
Metadata
Release files for popkit-mcp 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| popkit_mcp-1.0.3.tar.gz | 16.1 kB | Without provenance | Details for popkit_mcp-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| popkit_mcp-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for popkit_mcp-1.0.3-py3-none-any.whl |
Total release size: 33.8 kB
Release files / popkit_mcp-1.0.3.tar.gz
| Download URL | popkit_mcp-1.0.3.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ce0dba8a6a8fce2fbe9a4e79ef93262524bbe4911e3828901b0a9098c9269b5
|
|
BLAKE2b-256 checksum How to use checksums |
b346abb457e6fc131eabbaaee5e257ba64504436e4fa00759a874e1180168559
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / popkit_mcp-1.0.3-py3-none-any.whl
| Download URL | popkit_mcp-1.0.3-py3-none-any.whl |
|---|---|
| Size | 17.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8310a0a5ce7d67133ebdbc434acadcc490fcc54aa29ae60b289a3586040721d6
|
|
BLAKE2b-256 checksum How to use checksums |
a19d0974636d962a35b0edc2004f26171fdc393a8aaa55ea2d8a63482555a95b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Security for popkit-mcp 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.