Skip to main content
Glama
README.md
# Union MCP

An MCP server to use Union tasks, workflows, and apps as tools.

## Deployment Guides

Union MCP supports both Union v1 and v2. The following guides provide instructions
for deploying the MCP server for each version:

- [Union v1 MCP deployment](./guides/deployment_v1.md)
- [Union v2 MCP deployment](./guides/deployment_v2.md)

TDQS

C2.8/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have distinct purposes: get_execution and get_task retrieve specific items, list_tasks and list_workflows list collections, and run_task and run_workflow execute operations. However, get_task and list_tasks could potentially be confused if an agent isn't clear on whether it needs a single task or multiple tasks, as both relate to tasks in the same domain.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., get_execution, list_tasks, run_workflow). The naming is uniform across all six tools, with clear and predictable conventions that make it easy for agents to understand the action and target resource.

Tool Count5/5

With 6 tools, the count is well-scoped for a server focused on union execution, tasks, and workflows. It covers key operations like retrieval, listing, and execution without being overly sparse or bloated, fitting typical MCP server ranges of 3-15 tools.

Completeness4/5

The tool set provides good coverage for core operations in a union management domain, including getting items, listing collections, and running tasks/workflows. A minor gap exists in the lack of update or delete operations for tasks or workflows, which might limit full lifecycle management, but agents can still perform essential workflows with the available tools.

Maintenance

ActivityInactive
ResponsivenessNo issues