Harness Compatibility

Mon, 01 Jan 0001 00:00:00 +0000

processkit’s MCP servers are provider-neutral Python programs. They do not require aibox at runtime. aibox can install processkit, merge MCP configuration, pre-authorize processkit tools where a harness supports that, and supervise a managed devcontainer. Those are convenience and lifecycle features; they are not a processkit dependency.

For a direct install, point the harness at the desired server command inside the installed context/skills tree. The recommended one-process entry point is:

{
 "mcpServers": {
 "processkit-gateway": {
 "command": "uv",
 "args": [
 "run",
 "context/skills/processkit/processkit-gateway/mcp/server.py"
 ],
 "env": {
 "PROCESSKIT_MCP_MODE": "gateway"
 }
 }
 }
}

Current modes

Mode	Use when	Harness impact
Per-skill servers	You need fine-grained tool registration or the broadest compatibility.	The harness launches one stdio process per registered skill.
`aggregate-mcp`	You already use the legacy aggregate server.	One stdio process, compatibility name, no daemon behavior.
`processkit-gateway` stdio	You want the provider-neutral gateway surface now.	One stdio process, eager tool import, richer gateway metadata.
Daemon plus stdio proxy	You want a long-lived daemon with lightweight harness proxies.	One shared daemon plus one lightweight stdio proxy per harness.

The current gateway command is equivalent to:

MCP Servers on processkit

Harness Compatibility

Current modes