fix: MCP server token resolution and MISSIVE_API_KEY alias#1
Conversation
Posts are Missive's recommended approach for automations. Unlike drafts, they leave a visible trace and don't create ghost draft artifacts. Document that close != archive (no archive API exists). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The MCP server crashed on startup when configured with MISSIVE_API_KEY instead of MISSIVE_API_TOKEN. Now reuses the shared resolveToken() chain (env MISSIVE_API_TOKEN > MISSIVE_API_KEY > config file) instead of an inline env-only check. Also makes organization required for label commands and updates docs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
## [0.4.1](v0.4.0...v0.4.1) (2026-03-24) ### Bug Fixes * MCP server token resolution and MISSIVE_API_KEY alias ([#1](#1)) ([3f19757](3f19757))
|
🎉 This PR is included in version 0.4.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Summary
resolveToken()instead of inline env-only check, fixing crash whenMISSIVE_API_KEYis set instead ofMISSIVE_API_TOKENMISSIVE_API_TOKEN>MISSIVE_API_KEY> config file (~/.config/missive-ai/config.json)--organizationrequired forconv labelcommand (Missive API requires it)MISSIVE_API_KEYaliasTest plan
npx tsc --noEmitpassesMISSIVE_API_KEYenv var🤖 Generated with Claude Code