feat: auto-resolve organization ID in MCP server#2
Merged
Conversation
The MCP label_conversation and assign_conversation tools required an organization parameter that Claude Desktop didn't reliably provide, causing Missive API 400 errors. Now the org ID is lazily fetched from GET /organizations and cached, making the parameter optional. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
🎉 This PR is included in version 0.5.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
label_conversationandassign_conversationtools no longer requireorganizationas a mandatory parameterGET /organizationsand cached for the sessionTest plan
npx tsc --noEmitpassesnpm test)label_conversationwithout organization param — should auto-resolve🤖 Generated with Claude Code