Labsco
Ferdev logo

SwarmKit

from Ferdev

Inspectable coding sessions and workspace orchestration for software projects.

🔥🔥🔥✓ VerifiedFreeQuick setup
#git

SwarmKit Agent Kit

Reusable agent instructions and discovery metadata for using SwarmKit as an inspectable coding partner.

SwarmKit gives coding agents a shared workspace for software work: project state, inspectable sessions, claims, assignments, comments, links, artifacts, verification, PR links, and approval gates.

MCP Endpoint

SwarmKit's MCP endpoint is:

https://swarmkit.dev/api/v1/mcp

It uses Streamable HTTP and requires a bearer API token in the Authorization header:

Authorization: Bearer <SWARMKIT_TOKEN>

Public discovery:

  • https://swarmkit.dev/agents.txt
  • https://swarmkit.dev/.well-known/agents.json
  • https://swarmkit.dev/api/v1/mcp/skill.md
  • https://swarmkit.dev/api/v1/openapi.json

What Agents Should Do

  1. Call agent_context first.
  2. Inspect workspace and current work before creating a session.
  3. Prefer ensure_session_for_request for concrete user requests.
  4. Keep SwarmKit sessions updated with comments, links, artifacts, status, and verification.
  5. Use SwarmKit approval gates for PRs, deploys, deletes, meaningful spend, external sends, and cross-project changes.
  6. Complete a session only after the requested outcome is handled or a real blocker is recorded.

Registry Metadata

  • server.json is the official MCP Registry metadata for the remote SwarmKit MCP server.
  • glama.json marks this repo for Glama MCP indexing.
  • smithery-config-schema.json describes the token header mapping needed when publishing the remote MCP URL to Smithery.

Skill

The skill lives at:

skills/swarmkit-coding-partner/SKILL.md

It is intentionally portable across agent hosts that support Agent Skills.