Actor system for asyncio environments
Actor system for asyncio environments. The mindmesh mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.
class GreeterActor(BaseActor): def on_greet(self, msg: Greet) -> str: return f"Hello, {msg.name}!"
Everything the assistant can do here goes through one of these:
asyncio — native, zero external dependenciesfire-and — forget (tell) and request/response (ask) messagingBaseActor — Subclass BaseActor to define an actor. Each actor owns a private asyncio queue (its mailbox) and processes one message at a time - no parallelismActorHive — ActorHive is the registry and lifecycle manager. It creates, starts, and stops actorsActorAddr — ActorAddr is an opaque handle to an actor. It is the only way to interact with an actor from outside. Never hold a direct reference to an actortell — Enqueues any object as a fire-and-forget message. Returns immediatelyThe server ships on PyPI as mindmesh, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Mindmesh's toolset — asyncio, fire-and, BaseActor and 3 more — is a fair guide to whether it matches your workflow. It is maintained by Marcin Glinski; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Mindmesh's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| asyncio | native, zero external dependencies |
| fire-and | forget (tell) and request/response (ask) messaging |
| BaseActor | Subclass BaseActor to define an actor. Each actor owns a private asyncio queue (its mailbox) and processes one message at a time - no parallelism within a single actor. |
| ActorHive | ActorHive is the registry and lifecycle manager. It creates, starts, and stops actors. |
| ActorAddr | ActorAddr is an opaque handle to an actor. It is the only way to interact with an actor from outside. Never hold a direct reference to an actor instance. |
| tell | Enqueues any object as a fire-and-forget message. Returns immediately. |
{
"mcpServers": {
"mindmesh-1": {
"command": "uvx",
"args": ["mindmesh"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.