tinytown 0.10.0

A simple, fast multi-agent orchestration system using Redis for message passing
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77

# Townhall MCP Server

Tinytown includes an MCP server in the `townhall` binary for LLM/tooling integrations.

## Start MCP

```bash
# MCP over stdio (for local MCP clients)
townhall mcp-stdio

# MCP over HTTP/SSE
townhall mcp-http

# Override bind/port (default port = rest_port + 1)
townhall mcp-http --bind 127.0.0.1 --port 8081
```

## Registered MCP Tools

Read tools:

- `town.get_status`
- `agent.list`
- `agent.inbox`
- `task.list_pending`
- `backlog.list`

Write tools:

- `task.assign`
- `message.send`
- `backlog.add`
- `backlog.claim`
- `backlog.assign_all`
- `backlog.remove`

Agent-management/recovery tools:

- `agent.spawn`
- `agent.kill`
- `agent.restart`
- `agent.prune`
- `recovery.recover_agents`
- `recovery.reclaim_tasks`

Tool responses are JSON payloads wrapped as:

```json
{
  "success": true,
  "data": {},
  "error": null
}
```

## Registered MCP Resources

Static resources:

- `tinytown://town/current`
- `tinytown://agents`
- `tinytown://backlog`

Resource templates:

- `tinytown://agents/{agent_name}`
- `tinytown://tasks/{task_id}`

## Registered MCP Prompts

- `conductor.startup_context`
- `agent.role_hint` (`agent_name` required, `tags` optional)

## Notes

- MCP tools call the same Tinytown service layer used by CLI and REST.
- `mcp-http` uses Tower MCP's HTTP/SSE transport and follows standard MCP message semantics.