your ad here · $149/weekyour ad here · $149/weekyour ad here · $149/weekyour ad here · $149/weekyour ad here · $149/weekyour ad here · $149/weekyour ad here · $149/weekyour ad here · $149/weekyour ad here · $149/weekyour ad here · $149/weekyour ad here · $149/weekyour ad here · $149/week
William Collins

William Collins

@TheCloudGambitMaker

wcollins.ioLinkedIn
1
Launches
20
Upvotes received
1
Upvotes given
3
Comments

Launches

1 tool
  1. gridctlgridctl · One YAML file. One endpoint. Every MCP server plus the skills and agents you author alongside them20

Upvoted

1 tool
  1. gridctlgridctl · One YAML file. One endpoint. Every MCP server plus the skills and agents you author alongside them20

Comments

3 comments
  1. gridctl

    Commented on gridctl · Aug 24, 2026

    @Clemens - I added you on LinkedIn to discuss in DMs!

  2. gridctl

    Commented on gridctl · Aug 23, 2026

    @Zain Sheikh Great question, and yes! gridctl apply stack.yaml --watch diffs the YAML on save and applies adds/removes/edits without a restart. Policy blocks (skills exposure, limits, groups, clients) swap in memory; adding or removing an MCP server starts or stops that server. The grid changes still need a full apply. Skill files are a separate watcher: drop a SKILL.md in the registry and it shows up as a prompt even without --watch. You can also gridctl reload by hand.

  3. gridctl

    Commented on gridctl · Aug 19, 2026

    Agreed @Zain -> This was the whole reason behind the tool. Fun fact, I built this as a generic CLI tool on my own machine after MCP launched and didn't originally plan to open source it. Any good software out there usually comes from pain + friction.

Trending this week