This Repo is a mono repo for the king extension and the kingrt video call system. If you want to run the video call on a server you need to install the king-ext and then just use demo/video-chat. Kingrt can be testet on kingrt.com
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"king": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Systems-grade networking and infrastructure primitives for PHP
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication
An MCP server that securely interfaces with your iMessage database via the Model Context Protocol (MCP), allowing LLMs to query and analyze iMessage conversations. It includes robust phone number validation, attachment processing, contact management, group chat handling, and full support for sending and receiving messages.
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
MCP server for Kaseya Autotask PSA — 39 tools for companies, tickets, projects, time entries, and more
Email & SMS infrastructure for AI agents — send and receive real email and text messages programmatically
MCP Security Weekly
Get CVE alerts and security updates for King and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Systems-grade networking and infrastructure primitives for PHP
King turns PHP into a systems platform for transport-heavy, realtime, infrastructure-aware software. Instead of pushing critical networking, orchestration, discovery, storage, and control-plane work into sidecars, gateways, or glue layers, King keeps that work inside one native runtime that is directly available to PHP.
That changes what PHP can be used for. With King, PHP is no longer limited to short request handlers and thin application wrappers. It can own live sessions, streams, protocol state, routing decisions, telemetry, persistence, scaling signals, and cluster-facing workflows in one coherent runtime model.
The current line is beta. The repo-local baseline is green, the multi-backend object-store and control-plane surfaces are real, and the remaining closure work is now about narrower hardening, distributed-operating proof, and multi-node fleet behavior rather than placeholder subsystem stories.
If you do not have a Hetzner account yet, it is time to fix that. Use the Hetzner Cloud referral link and you help support the live infrastructure tests that keep King honest.
For a repository-local build:
git clone --recurse-submodules https://github.com/Intelligent-Intern/king.git
cd king
./infra/scripts/build-profile.sh release
php -d extension="$(pwd)/extension/modules/king.so" -r 'echo king_version(), PHP_EOL;'
That gives you the extension plus the matching QUIC runtime artifacts for the
local release profile. If you only want the extension build, use
./infra/scripts/build-extension.sh.
If you want the beginner path from zero to a local WebSocket roundtrip, start with documentation/getting-started.md.
King also ships a
PIE install path. PIE is the successor to PECL.
Tagged releases that publish the matching PIE source asset can be installed
with pie install intelligent-intern/king-ext. Packaging details and local
verification steps live in
documentation/pie-install.md.
One good first King application is this:
/watch?bucket=inboxPOST /upload?bucket=inbox&object=demo.txtThe event looks like this:
{
"event": "object.available",
"bucket": "inbox",
"object_id": "demo.txt",
"content_type": "text/plain",
"size": 1234
}
The important point is that the durable write and the realtime fanout happen in the same native runtime. The object lands in King storage, and the same PHP process can immediately push the event over live WebSocket handles without ha