📡 MCP Radar

larstalian/tincan

Your team's coding agents talking to each other across machines: a live directory of who's working on what, plus messages. Peer to peer, no server.

⭐ 12 stars
⑂ 0 forks
Rust
momentum ▲ 60.0
created 2026-10-11
on radar since 2026-10-13
ai-agentsclaude-codecodexcoding-agentscursordeveloper-toolsgemini-cliirohmcpp2prust
View on GitHub ↗Homepage ↗

About tincan

Your team's coding agents, talking to each other. Every agent session on every teammate's machine can see who's working on what right now, and message the right session directly. Claude Code, Codex, Cursor, Gemini, Copilot, opencode, pi and Reason. Peer to peer, no server.

One person runs this and picks a team name:

You get a team link (it's on your clipboard). Send it to your friends: they open it, paste one command, type their name, and they're in. Or they just tell their agent "join my tincan team: ".

That's it. Ask any agent "who's on the team?", or tell it to ask someone's agent something.

- Every agent on the team. Agents get three tools: listteam, sendmessage, checkinbox. They never have to report anything: what a session is doing comes from its own title and todo list. - Messages land right away. Claude Code, Codex, opencode, pi and Reason get them mid-session, and idle ones wake up; Cursor, Gemini and Copilot at their next step. Claude sessions you already had open join without a restart. - A menu bar icon on macOS shows who's online and what they're doing. - No setup to maintain. It runs in the background, updates itself, and the link keeps working.

Each machine runs a small daemon. Teammates' machines connect directly (on the same Wi-Fi, or through the internet with iroh); if that fails, traffic goes through a relay that only sees encrypted bytes. That's one of n0's (the company behind iroh) unless your team runs its own (tincan relay ): then your machines never contact n0 at all. Only team members can connect, and a machine can only speak for its own person

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/larstalian--tincan.html)

Related MCP servers

Kaseban/baton

Convert AI coding sessions between Claude Code, Codex, OpenCode, Zed, Aider, Gemini CLI, Cursor, Cline & more — lossless, round-trip tested. MCP server + CLI.

⭐ 4Rust
NiazMorshed2007/jev-review

Local-first MCP plugin for continuous software-quality review by AI coding agents, powered by Jev.

⭐ 209TypeScript
Get-Concord-AI/concord-mcp

Shared work-state for coding agents: claim work, leave handoffs, and generate review packets before PRs, over MCP.

⭐ 6TypeScript
Novaya-AI/novgraph

Open-source client for Novgraph, Novaya's proprietary hosted code knowledge graph. Gives coding agents recorded intent, related-code context, ranked change impact and architecture context over MCP or

⭐ 6Python
kdev1966/Handoff-CLI

Shared, persistent memory for your AI coding assistants (Claude Code, Copilot, Cursor, Gemini CLI, Codex…): a local MCP server and CLI that hand work over between tools automatically.

⭐ 5Python
doominkim/illithid

One library of rules, skills, subagents and MCP servers for Claude Code, Codex, OpenCode, Gemini CLI and GitHub Copilot. Edit once, synced to every tool.

⭐ 4TypeScript

📬 Get the weekly radar in your inbox

The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.