Extend searchSpaces to support folder_id#19
Closed
sebastienheyd wants to merge 4 commits into
Closed
Conversation
Add folder_id parameter to searchSpaces tool to resolve a ClickUp folder by its ID. This avoids creating a separate MCP tool. Changes: - Add getFolderDetails() in utils.ts with promise-based caching - Add formatFolderTree() to format folder tree structure - Add folder_id parameter to Zod schema and handler - Add test covering folder_id case - Update searchSpaces description in manifest.json
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a33d4ee7b9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
added 2 commits
March 3, 2026 13:55
All tools accepting a `task_id` parameter (getTaskById, addComment, updateTask, searchTasks) now accept custom task IDs in addition to internal IDs. Custom IDs are automatically resolved to internal IDs via the ClickUp API. - Add isCustomTaskId(), resolveCustomTaskId(), and resolveTaskId() helpers - Update tool schemas to accept both ID formats - Add custom ID resolution logic to search tools - Update manifest and CHANGELOG
- Change package name from @hauptsache.net/clickup-mcp to @sebastienheyd/clickup-mcp - Update all GitHub repository references to sebastienheyd/clickup-mcp - Update manifest and package.json metadata - Add contributor credit for Sébastien HEYD - Update installation examples and documentation links
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
folder_idparameter tosearchSpacestool to resolve a ClickUp folder by its IDgetFolderDetails()utility with promise-based caching (same pattern asgetSpaceDetails)formatFolderTree()to format folder tree structure (lists, statuses, parent space)This is the alternative approach suggested by @Nemo64 in #17: instead of creating a separate
getFolderInfotool, this integrates folder resolution directly intosearchSpaces. Whenfolder_idis provided, the tool returns folder details (lists, statuses, parent space) and ignores thetermsparameter.Test plan
npm run buildcompiles without errorsnpm run testall 32 tests pass (including new folder_id test)npm run cli searchSpaces folder_id="<a_folder_id>"returns folder info