Misarmail Mcp
C 63 completed
Other
api / yaml · tiny
40
Files
1,936
LOC
0
Frameworks
4
Languages
Pipeline State
completedRun ID
#1520743Phase
doneProgress
0%Started
2026-04-16 14:09:55Finished
2026-04-16 14:09:55LLM tokens
0Pipeline Metadata
Stage
SkippedDecision
skip_scaffold_dupNovelty
21.79Framework unique
—Isolation
—Last stage change
2026-04-16 18:15:42Deduplication group #49966
Member of a group with 15 similar repo(s) — canonical #189399 view group →
All rows scored by the Repobility analyzer (https://repobility.com)
AI Prompt
Create a backend service that exposes the full MisarMail email marketing platform via the Model Context Protocol (MCP). I need this server to handle interactions using HTTP streaming and support OAuth 2.0 (PKCE) plus API Key authentication. The system should expose 32 tools covering areas like email, campaigns, contacts, and analytics, and also include 11 pre-built skills. Please structure the project to be easily callable from any MCP-compatible AI client, and include setup instructions for running it locally, perhaps using Docker.
api mcp email-marketing backend http oauth2 docker javascript yaml json
Generated by gemma4:latest
Catalog Information
Create a backend service that exposes the full MisarMail email marketing platform via the Model Context Protocol (MCP). I need this server to handle interactions using HTTP streaming and support OAuth 2.0 (PKCE) plus API Key authentication. The system should expose 32 tools covering areas like email, campaigns, contacts, and analytics, and also include 11 pre-built skills. Please structure the project to be easily callable from any MCP-compatible AI client, and include setup instructions for run
Tags
api mcp email-marketing backend http oauth2 docker javascript yaml json
Quality Score
C
62.9/100
Structure
58
Code Quality
90
Documentation
41
Testing
15
Practices
69
Security
100
Dependencies
70
Strengths
- CI/CD pipeline configured (github_actions)
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
- Containerized deployment (Docker)
- Properly licensed project
Weaknesses
- No tests found — high risk of regressions
Recommendations
- Add a test suite — start with critical path integration tests
- Add a linter configuration to enforce code style consistency
Languages
Frameworks
None detected
Symbols
variable10
constant2
Embed Badge
Add to your README:
