Skip to main content
Glama
Sign In
enesjakozh
Union MCP

Union MCP

by unionai-oss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

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:

Available Tools

6 tools
get_executionD

Get personalized union execution.

Inputs: domain (required), name (required), project (required).

get_taskD

Get a union task.

Inputs: domain (required), name (required), project (required). Returns: result

list_tasksC

List all tasks in a project and domain.

Inputs: domain (required), project (required). Returns: result

list_workflowsC

List all workflows in a project and domain.

Inputs: domain (required), project (required). Returns: result

run_taskC

Run a task with natural language.

- Based on the prompt and inputs dictionary, determine the task to run
- Format the inputs dictionary so that it matches the task function signature
- Invoke the task

Args:
    project: Project to run the task in.
    domain: Domain to run the task in.
    name: Name of the task to run.
    inputs: A dictionary of inputs to the task.

Returns:
    A dictionary of outputs from the task.

Inputs: domain (required), inputs (required), name (required), project (required). Returns: result

run_workflowB

Run a workflow with natural language.

- Based on the prompt and inputs dictionary, determine the workflow to run
- Format the inputs dictionary so that it matches the workflow function signature
- Invoke the workflow

Args:
    project: Project to run the workflow in.
    domain: Domain to run the workflow in.
    name: Name of the task to run.
    inputs: A dictionary of inputs to the workflow.

Returns:
    A dictionary of outputs from the workflow.

Inputs: domain (required), inputs (required), name (required), project (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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 recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches