sdr-mcp
CLAUDE.md9 starsChanged 5 months agoMITView on GitHub
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/architect.mdcCursor rule
- .cursor/rules/token-budget.mdcCursor rule
- llms-full.txtllms.txt
- llms.txtllms.txt
- full-stack-developerSkill
- mcp-server-architectSkill
The file
We found no rules to list in this file: it reads as prose or reference rather than instructions.
Files
sdr-mcp — Claude Code Guide
Overview
SDR (Software Defined Radio) MCP Server
Entry Points
uv run sdr-mcp→sdr_mcp.cli:main
Standards
- FastMCP 3.2+ portmanteau tool pattern — tools use
operationenum param - Responses: structured dicts with
success,message, domain-specific fields - Dual transport: stdio (Claude Desktop) + HTTP (
MCP_TRANSPORT=http) - See mcp-central-docs for fleet-wide coding standards
Key Files
README.md— full documentationpyproject.toml— build config and entry pointsAGENTS.md— OpenAI Codex agent context (if present)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.