Morrow Desk MCP Server
Enables operators to manage support desk operations, including case queues, customer relationships, and communications, through an agent-first MCP interface with exact lifecycle and authorization controls.
README
Able
Able is an open-source, agent-first ERP for service businesses. It is designed as a set of deep business modules that agents can operate through small, task-shaped interfaces without collapsing the business into generic CRUD.
Able Desk is the first application. It combines a support desk, customer directory, CRM, communications inbox, durable operations, and controlled improvement records on Cloudflare Workers. MCP is the normal operator interface; customers use an accessible support portal and approved channels; /ops is a small Cloudflare Access-protected recovery surface.
Project status: early V1. The architecture and core Desk flows are implemented and tested, but Able does not yet claim production readiness. A deployed Worker is not, by itself, an operational support desk.
Project site · V1 contract · Roadmap · Architecture overview · Architecture reference
Why agent-first
The normal Desk loop is intentionally small:
able_case_nextreturns a complete decision workspace.able_case_replycommits a reply against its exact opaque revision.
The module—not the agent or transport adapter—owns lifecycle policy, authorization, audit evidence, idempotency, delivery intent, and concurrency checks. MCP, the portal, email, WhatsApp, and /ops authenticate, translate, and render.
What Desk V1 includes
- Case queues, search, assignment, priority, lifecycle, public replies, and private notes
- Public knowledge, request intake, private case links, attachments, and bounded attachment evidence
- Browser text help, optional voice input, and optional read-only Shopify order lookup
- Channel-neutral conversations with explicit routing to support, sales, both, or no work
- Signed WhatsApp text ingress and conversation-owned replies
- Canonical parties, CRM relationships, sourced activities, and scheduled follow-ups
- Durable operations, immutable receipts, outcome observations, and inactive evaluation-gated improvements
- Cloudflare Access identity for MCP and
/ops, plus a public portal protected by capabilities and Turnstile - D1, private R2 objects, Workers AI, Cloudflare Email Service, and a durable outbox
The exact scope and exclusions are binding in docs/product-v1.md.
Repository structure
able/
├── apps/
│ └── desk/ # Buildable Desk Worker, migrations, tests, assets, and configs
├── packages/ # Future reusable modules, extracted only behind proven interfaces
├── docs/ # Product contract, architecture visuals, ADRs, deployment, and roadmap
├── scripts/ # Repository-wide publication and history gates
└── .github/ # CI, security scanning, and contributor templates
Desk remains one honest buildable workspace for the first public release. Modules will move to packages/ only when each has an independent interface and test boundary; see packages/README.md.
Develop
Requirements: Node.js 22 or 24+, npm, and a Cloudflare account for remote deployment.
npm install
npm run db:migrate:local
npm run dev
Copy apps/desk/.dev.vars.example to apps/desk/.dev.vars for local-only values. Never commit the resulting file.
Run the complete local gate before opening a pull request:
npm run check
Changes to voice prompts or tool descriptions also require:
npm run eval:voice
Upstream and proving deployments
This repository is the canonical development source. Hosted proving grounds deploy exact commits through protected environments; they are not private product forks. Tenant secrets, resource coordinates, content, customer data, and operational runbooks remain outside source control. A lesson found in a proving deployment becomes a generic issue, neutral test, and upstream change here.
See docs/development.md for the full workflow and docs/deployment.md for the deployment boundary.
Community
Questions belong in Discussions; bugs and proposals belong in issues. See CONTRIBUTING.md, GOVERNANCE.md, SECURITY.md, and CODE_OF_CONDUCT.md.
Able is licensed under Apache-2.0.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。