The Architecture
All API calls route through MorphixAI's proxy. You authenticate each platform once via OAuth on morphix.app/connections, and the proxy handles token refresh, rate limiting, and error mapping.
Setup in 60 Seconds
# Install the plugin
openclaw plugins install openclaw-morphixai
# Add your API key
echo "MORPHIXAI_API_KEY=mk_your_key_here" >> ~/.openclaw/.env
# Restart OpenClaw
openclaw gateway restart
That's it. No per-service config files. No token juggling.
What Can It Do?
Daily Standup -- My Favorite Skill
Every morning I type standup and get a morning briefing that aggregates your pending GitLab MRs, Jira issues due this week, unread emails, and today's calendar events. One prompt replaces 15 minutes of tab-switching.
Cross-Platform Workflows
The real power is combining tools. Ask your agent to "Create a GitLab MR for Jira issue TANKA-1234" and it reads the Jira issue, creates a branch, opens the MR with context, and transitions the Jira status automatically.
Available Tools
12 tools covering GitLab, GitHub, Jira, Confluence, Outlook Mail, Outlook Calendar, MS To Do, Gmail, Google Tasks, Notion, Figma, and MorphixAI account management.
Why a Proxy?
- One key vs. eleven -- Simpler secrets management
- OAuth handled -- Token refresh managed centrally
- Unified error handling -- Consistent format across platforms
- Rate limiting -- The proxy manages per-platform limits
- Security -- Your tokens live on MorphixAI's servers, not in config files
What's Next
We're planning integrations for Feishu (Lark), DingTalk, WeCom, and Gitee.
Get Started
openclaw plugins install openclaw-morphixai
- npm
- GitHub (MIT)
- ClawHub Skills
- Get API Key
Questions? Feedback? Open an issue or drop a comment below.
Top comments (0)