AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
MCP verified MIT Self-run

Inbox Sherpa

mcp-mihai-codes-inbox-sherpa · by Mihai-Codes

Local-first mail intelligence system: MyMX inbound email → prioritization → Beeper/CodeBeep alerts

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add mcp-mihai-codes-inbox-sherpa

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ● Environment & secrets Used
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Inbox Sherpa? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Inbox Sherpa

Inbox Sherpa is a local-first mail intelligence system that ingests inbound email via MyMX webhooks, prioritizes what matters, and notifies you through your preferred channel (Matrix/Beeper, ntfy, Slack, Discord, Telegram, Pushover-style, or generic webhooks). The goal: you stop checking mail and only get alerts for high‑value messages.

MVP goals

  • Receive inbound email webhooks (MyMX)
  • Verify webhook signatures
  • Normalize/store email payloads
  • Score/prioritize messages (people, AI news, waitlist acceptances, etc.)
  • Send concise notifications via a pluggable notifier
  • Provide rules for allow/block/unsubscribe + safety flags

Repository layout

apps/
  webhook-receiver/      # Node/TS webhook endpoint
docs/
  vision.md              # Product vision + use cases
  architecture.md        # Data flow + components
  student-benefits.md    # Free programs & credits
  beta-access-email.md   # MyMX beta request email
  roadmap.md             # Next steps

Quick start (dev)

cd apps/webhook-receiver
npm install
npm run dev

Environment

See .env.example in apps/webhook-receiver.

Local dev mode (no signature verification)

Set DEV_MODE=true and POST a MyMX-style JSON payload to /webhook/mymx/dev.

Notifications (pluggable)

Supported channels (MVP):

  • Matrix/Beeper (recommended for local-first). Works great with CodeBeep.
  • ntfy (simple, free, self-hostable): https://ntfy.sh
  • Slack Incoming Webhooks: https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks
  • Discord Webhooks: https://docs.discord.com/developers/resources/webhook
  • Telegram Bot API: https://telegram-bot-sdk.readme.io/reference/sendmessage
  • Generic webhook (POST JSON)

Fallbacks:

  • Set NOTIFIER and NOTIFIER_FALLBACK to chain delivery (e.g., matrix → ntfy).

If MATRIX_ROOM_ID is not set, Inbox Sherpa will auto-create a private room using your Matrix access token and store the room ID in MATRIX_ROOM_STORE.

Notes

  • Webhook handler must be idempotent (same event ID can be retried).
  • MyMX signature verification is required in production.
  • Store secrets in env; never commit.

References

  • MyMX docs: https://mymx.dev/docs
  • Webhook payload: https://mymx.dev/docs/webhook-payload

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Communication