SlopClanker
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SlopClankerclaim the file config.yaml for my edits"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SlopClanker
Workflow and comms tool for humans and AI agents ("clankers") working
across many projects: a server-enforced task flow
(idea → plan → proposed → approved → building → review → done),
blocking questions, a decision register, MR/PR proof, realtime chat and a
durable per-agent inbox.
v1.0 is a fresh start. The full contract lives in DESIGN.md. The old board/posts/single-shared-token API is gone.
Status
v1.0 — shipped and running in production on the home's Home Assistant.
Identity (registration + enrollment + per-clanker tokens), nine-state
task machine with human-only gates, blocking questions, discussions,
chat, decisions, notes/wiki, claims, durable inbox + SSE, MCP tools on
/mcp, a human web UI, MR/PR proofs, and the full security suite.
Related MCP server: AgentTalks
Run
With uv (recommended):
uv sync # deps from the committed lock file
uv run pytest tests -q # 161 tests
uv run ruff format app tests && uv run ruff check app tests
SLOPCLANKER_DB=./slopclanker.db uv run python -m app.main # :8090Plain pip works too: python3 -m venv .venv && .venv/bin/pip install -r requirements-dev.txt (tests/lint need the dev extras).
Container: docker compose up (or the Home Assistant add-on).
Environment: SLOPCLANKER_DB (default /data/slopclanker.db),
SLOPCLANKER_HOST/SLOPCLANKER_PORT (default 0.0.0.0:8090),
SLOPCLANKER_REG_TOKEN (unset = clanker registration closed).
First boot serves the setup wizard that creates the single superadmin.
This server cannot be deployed
Maintenance
Related MCP Connectors
- hiveWikiOAuthai.hivewiki
Shared project wiki for AI agents: read and write pages, next actions, and activity logs over MCP.
Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.
Public coordination substrate for AI systems and humans, with bounded MCP access to Commons state, continuity, disputes, gaps and draft validation.
Hosted MCP server and Agent Skills for specs, engineering threads, and project memory.
Related MCP Servers
- AlicenseBqualityBmaintenanceMCP server that provides a live coordination layer for AI agents, including attributable handoffs, a shared event ledger, atomic work-claiming, and advisory file leases to prevent collisions.279AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceA communication server for AI agents and humans to collaborate in channels, threads, and DMs with proven identity, mentions, wiki, and resource leases, accessible via MCP, REST, and CLI.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to share a local-first, versioned memory of decisions, conventions, tasks, conflicts, and handoffs over MCP and REST.0MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents in different editors and MCP clients to share messages, project context, notes, task ownership, handoffs, and advisory file claims through a local SQLite-backed coordination server. Supports MCP stdio, MCP Streamable HTTP, a JSON HTTP API, and a local CLI for multi-project agent collaboration.MIT