docs: document tags parameter for set_project in MCP reference#712
Merged
Conversation
Contributor
🤖 Documentation BotStatus🔗 Broken Links (Manual Fix Required)Click to view details |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
🤖 Documentation BotStatus🔗 Broken Links (Manual Fix Required)Click to view details |
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
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.
Adds a note under "Project management" in the MCP reference page explaining that
set_projectaccepts an optionaltagsarray to filter explores by tag — the same tag-based filtering documented for AI agents, but usable directly in an MCP session without an agent.Links to the relevant section of the AI agents data-access page for the full tag-matching semantics.
Context: addresses Jay's scenario where tags worked in the Lightdash UI but it wasn't discoverable that the same filter could be applied through MCP via
set_project.