Repository navigation
Replies: 1 comment
|
Thanks, @b-gutman, for the proposal and for offering both options. We'd prefer the opt-in one: a third-party MCP configuration in your own repository, using the existing Claude Code and Codex runtime fragments and a profile that selects them, rather than adding Pipeworx to OpenRig's shared defaults. A small repository showing a useful task, setup and removal, tested versions and the service's current limits would be welcome; link it here so people can try it. This doesn't need a new Core API or registry. We haven't established a general enough use case to make it a default for teams that use our shared configuration. |
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.
Would you take Pipeworx (gateway.pipeworx.io/mcp) as a third default in the shared MCP fragment next to Exa and Context7? It's live public data. It works with no key up to 50 requests a day, and a free signup raises that to 200. I'm happy to send the PR (three fragments, one test, one README line) or keep it as an opt-in package if you'd rather.
All reactions