Default API version to dev and add Change Item Position tool #44
Conversation
lorenzowritescode
changed the title
| description: 'Monday API version', | ||
| required: false, | ||
| defaultValue: undefined, | ||
| defaultValue: "dev", |
There was a problem hiding this comment.
Hey we dont do it on purpose, the mcp uses the current version by default
| @@ -1,2 +1,5 @@ | |||
| #!/bin/bash | |||
| curl "https://api.monday.com/v2/get_schema?format=sdl&version=stable" -o src/monday-graphql/schema.graphql | |||
| API_VERSION="dev" | |||
There was a problem hiding this comment.
The MCP works against the current not dev as its what users use
There was a problem hiding this comment.
if in theory we add a tool from dev we should have diffrentet fetch schema for it
There was a problem hiding this comment.
Why not work on the dev version by default in the MCP? In the MCP the contract with the user are the tools - and even then this is mediated by the agent. I don't think there's anything to lose by working on latest, if anything it makes the MCP more useful
| }; | ||
| export type ChangeItemPositionToolInput = typeof changeItemPositionToolSchema; | ||
|
|
||
| const MIN_API_VERSION = '2025-10'; |
There was a problem hiding this comment.
In theory, what we need to do here is that if users use a different API version, they won't have access to the tools at all
I think its safer to make sure the mcp works against stable API version because of it, but we can change it to work against rc if needed maybe?
@gregra81
2 participants
I think we should default the API version of the graphql package to
devin order to get the latest available improvements in our graphQL API.I think the agent model has enough flexibility (unlike a traditional integration) to deal with API changes.
Demo of new tool:
change-item-position-mcp-demo.mp4