Replies: 1 comment
|
I made a CLI and skill for doing this, so far working well. i may share, its not hard, but tried to make it easy for an agent to understand/follow without needing the skill (just needs to know its there) and with failure responses meant to lead llm to fix the request
each also give you options to list things and i did try to break them down a bit. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Per CONTRIBUTING.md, opening this for community feedback before merging new tooling. Related PR: (#352
What this solves
Every integration today (Cursor rules, Aider conventions, Windsurf rules) requires running shell scripts and copying static files. There's no way to programmatically discover, search, or compose agents at runtime.
What I built
An MCP server (integrations/mcp-server/) that turns all 161 agent markdown files into a live, queryable registry. Any MCP-compatible client (Cursor, Claude Code, Claude Desktop) can dynamically interact with the full agent catalog without manual file management.
Tools
Resources
How it works
{ "mcpServers": { "agency-agents": { "command": "bun", "args": ["run", "/path/to/agency-agents/integrations/mcp-server/src/index.ts"] } } }"Search for agents that can help with API security"
"Compose a team of 5 for building a SaaS MVP"
"Get the full prompt for the Security Engineer agent"
Technical details
PR
Implementation is in PR #352.
Happy to iterate on the approach based on community feedback.
All reactions