feat(scripts): add push to mcp-node on release#4784
Conversation
✔️ Code generated!
📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
| tags: | ||
| - abtest | ||
| operationId: listABTests | ||
| x-mcp-tool: true |
There was a problem hiding this comment.
as per @kombucha's comment this might be easier/better to handle at the mcp repository level, unless we see some documentation purposes that we want to reflect on our API reference pages?
There was a problem hiding this comment.
Could be indeed reflected in the documentation at some point! I'd stick with your solution !
There was a problem hiding this comment.
I think this metadata should leave in the source of truth (ie this repository) eventually, I just thought we might want to experiment first in the mcp repo while we're figuring things out before doing it here; especially if we start defining mcp specific description.
Also we might want to think whether we want to opt-in endpoints vs opt-out depending on the ratio.
With that being said, maybe the push mecanism already makes it comfortable to contribute here directly 😄
There was a problem hiding this comment.
you see that as a non blocker so? We can also make it clearer that this is where the source of truth lives if a PR is opened on the mcp side as well, the good part of having it here is mostly reflecting it from the documentation
morganleroi
left a comment
There was a problem hiding this comment.
God save the OpenAPI spec!
…kip ci] Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
algolia/api-clients-automation#4784 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
🧭 What and Why
🎟 JIRA Ticket:
Changes included:
This PR adds mcp-node to the repository to spread the specs to, it also updates the support for JSON output as this is what's expected there.