weaver-mcp
Related Servers
Alternatives to weaver-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for Weaver OA Ecology E9, enabling workflow management, organizational queries, and file uploads. Automatically handles authentication and RSA encryption for secure API calls.5MIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server provides tools to interact with the AgileWorks business process platform via its Web API, enabling document management, workflow operations, user administration, and more.1MIT
- FlicenseNot gradedqualityCmaintenanceThis MCP server enables managing DingTalk OA approval processes via the official OpenAPI, supporting approval detail queries, attachment downloads, and approval workflow actions such as starting, approving, rejecting, and revoking instances, with security features like fixed caller and allowlist.-
- FlicenseNot gradedqualityDmaintenanceThis MCP server simplifies interaction with the ConnectWise Manage API through API discovery, execution, and a fast memory system for efficient workflows.4 npm-
- AlicenseAqualityDmaintenanceMCP server for Mybatis-Flex ORM framework providing API documentation, code examples, and changelog queries.410 npm1MIT
- AlicenseAqualityBmaintenanceAn MCP (Model Context Protocol) server that enables integration with the Simplifier Low Code Platform. This server provides tools and capabilities for creating and managing Simplifier Connectors and BusinessObjects through the platform's REST API.17382 npm5MIT
TDQS
Scored across 10 tools
Most tools have clear, distinct purposes, especially the status-specific workflow lists (todo, my, processed, all) and the composite detail fetcher. Some overlap exists between list_program_modification_workflows and list_all_workflows with the default workflow id, but descriptions are detailed enough to guide selection.
Tool names consistently follow a verb_noun snake_case pattern, such as list_*, get_*, query_*, and submit_*. Minor asymmetry like get_workflow_detail versus list_*_workflows is negligible and does not hurt predictability.
Ten tools is a reasonable, well-scoped surface for an OA workflow integration. Each tool covers a distinct need: connection testing, employee lookup, workflow listing by status, workflow details, and report submission.
Read-oriented workflow coverage is solid with list, detail, and status-specific queries, plus one submission workflow. However, there are notable gaps: no approve/reject actions for todo workflows, no generic process submission, and no update/cancel operations for existing workflows.