Radar
Add a Claude Code marketplace plugin that scans your local sessions, MCP config, and goals to surface ecosystem changes that matter to your active stack.
Overview
Radar is a plugin marketplace for the Idea phase that recommends relevant AI ecosystem updates based on your local Claude Code and Cowork session history.
What is this marketplace?
- Parses Claude Code project sessions and Cowork history locally—prompts, tool calls, and failures—without sending that hi
- Scores recommendations with an explicit rubric including usageGap tied to gaps visible in your session data
- Reads installed MCP servers (.mcp.json), allowed tools (settings.json), plugins, CLAUDE.md goals, and dismissal history
- Install flow: marketplace add flippyhead/radar plus plugin install radar@flippyhead/radar
- Positions as ecosystem radar when Claude features, dependencies, and MCP servers shift weekly while you ship
- Marketplace lists 1 plugin in catalog ingest metadata
- README states zero setup beyond install and that data stays local
Community signal: 3 GitHub stars.
What problem does it solve?
The agent tooling landscape moves faster than a solo builder can read, yet generic digests ignore the prompts, failures, and MCP stack you actually use.
Who is it for?
Claude Code power users juggling multiple repos, MCP servers, and weekly platform updates who want signal tied to their own transcripts.
Skip if: Builders who want a hosted analytics SaaS with team-wide dashboards and no local session parsing.
What do I get? / Deliverables
After install, you get locally grounded, scored recommendations aligned to your projects, tooling, and stated goals instead of one-size-fits-all news.
- Registered flippyhead/radar marketplace and installed radar plugin
- Ongoing locally parsed recommendations weighted by your tooling, goals, and dismissals
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Idea / Discover is the canonical shelf because Radar’s core job is oriented discovery of what changed in AI tooling relative to your work, not building a feature in-repo. Discover fits personalized digests grounded in ~/.claude/projects history, Cowork chats, installed plugins, and CLAUDE.md priorities instead of generic newsletters.
How it compares
Personalized local ecosystem radar plugin, not a generic SEO or content marketing skill.
Common Questions / FAQ
Who is Radar for?
Solo developers on Claude Code who need curated tooling and dependency signals filtered through their real prompts, failures, and installed plugins.
When should I use Radar?
Use it when you are choosing what to adopt next—new Claude features, MCP servers, or major dependency moves—without pausing shipping for manual news scanning.
How do I add Radar to my agent?
Run `/plugin marketplace add flippyhead/Radar` then `/plugin install Radar@flippyhead/Radar` in Claude Code as documented in the README install block.