convez.ai
MCP ServerIntegração & APIsIntermediário
Uluops

UluOps Registry MCP

Uluops/-uluops-registry-mcp

Gerencie definições de workflows e agentes de IA via MCP com 44 ferramentas integradas

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que integra Claude e outras ferramentas com a API do UluOps Registry, oferecendo 44 ferramentas para gerenciar, versionar e validar definições de workflows, agentes e pipelines de IA. Funciona como cliente fino que traduz protocolos entre MCP e a API REST do backend.

Instalação

$npx convez-ai Uluops/-uluops-registry-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
37%
Último commit
há 1 semana
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Criar e validar definições de agentes e workflows antes de publicar
  • Buscar e reutilizar definições já publicadas no registro compartilhado
  • Versionar e controlar histórico de mudanças em pipelines de IA
  • Analisar métricas e desempenho de workflows em produção

Veredito

MCP server robusto e bem-arquitetado para gerenciamento centralizado de workflows em IA. Segue padrão thin client, delegando lógica ao backend, o que reduz complexidade local mas requer acesso contínuo à API UluOps. Ideal para equipes usando Claude Code ou OpenCode que precisam de registry compartilhado.

README

A tradução para o português deste README ainda está na fila.

UluOps · Operating Intelligence as Infrastructure


@uluops/registry-mcp

npm version License: MIT Node.js Version TypeScript Tests

MCP (Model Context Protocol) server for the UluOps Registry API. Provides 44 tools and 4 resources that let Claude Code, OpenCode, Gemini CLI, and other MCP-compatible harnesses browse, create, validate, version, and analyze AI workflow definitions (agents, commands, workflows, pipelines).

Quick start

The recommended way to install this is via @uluops/setup, which writes the MCP config for you:

npx @uluops/setup

If you'd rather wire it up by hand, add this block to your harness's MCP config (e.g. ~/.claude.json for Claude Code, ~/.config/opencode/opencode.json for OpenCode):

{
  "mcpServers": {
    "uluops-registry": {
      "command": "npx",
      "args": ["-y", "@uluops/registry-mcp"],
      "env": {
        "ULUOPS_API_KEY": "your-api-key"
      }
    }
  }
}

Get an API key at app.uluops.ai/settings/api-keys, then restart your harness.

Configuration

All configuration is passed via environment variables in the env block. No .env file is needed.

VariableDescriptionRequiredDefault
ULUOPS_API_KEYAPI authentication keyYes—
ULUOPS_ORG_SLUGOrganization slug for scoped requestsNo—
ULUOPS_REGISTRY_TIMEOUTRequest timeout (ms)No30000
ULUOPS_REGISTRY_RETRIESRetry attemptsNo3
LOG_LEVELLogging level (error, warn, info, debug)Noinfo
ENABLE_FILE_LOGGINGWrite logs to diskNofalse
LOG_DIRLog file directoryNo./logs
VERBOSE_LOGGINGVerbose security decision loggingNofalse
LOG_PERFORMANCE_METRICSLog performance metricsNofalse
WORKSPACE_DIRBase directory for file_path containment (CWE-22 protection)Nocwd
OUTPUT_BASE_DIRBase directory for output_path containment (CWE-22 protection)Nocwd

Design philosophy

Thin client pattern. This MCP server contains zero business logic. All data processing, validation, storage, and rendering are handled by the registry API. The server's sole responsibility is protocol translation between MCP's stdio JSON-RPC and the backend REST API.

Quick examples

Once configured, your harness can invoke these tools through MCP:

// Browse published definitions
list_definitions({ "type": "agent", "status": "published", "limit": 10 })

// Get a specific definition with its rendered YAML
get_definition({ type: "agent", name: "code-validator", include_yaml: true })

// Search across all definition types
search_definitions({ query: "validation", type: "agent" })

// Validate YAML before publishing (inline or by file path)
validate_definition({ type: "agent", yaml: "..." })
validate_definition({ type: "agent", file_path: "/path/to/agent.yaml" })

// Create and publish a definition
create_definition({ type: "agent", name: "my-agent", yaml: "..." })
publish_definition({ type: "agent", name: "my-agent", version: "1.0.0" })

// One-call create-or-update-and-publish
update_and_publish({ type: "agent", name: "my-agent", version: "1.1.0", yaml: "..." })

// Compare versions in three different formats
diff_versions({ type: "agent", name: "code-validator", from: "1.0.0", to: "1.1.0" })                  // section summary
diff_versions({ type: "agent", name: "code-validator", from: "1.0.0", to: "1.1.0", format: "fields" })  // structural diff + suggested bump
diff_versions({ type: "agent", name: "code-validator", from: "1.0.0", to: "1.1.0", format: "unified" }) // git-style diff

// Analytics
get_effectiveness({ type: "agent", name: "code-validator", version: "1.1.0" })
compare_effectiveness({ type: "agent", name: "code-validator", versions: ["1.0.0", "1.1.0"] })

Available tools

Core tools (P0)

ToolDescription
list_definitionsList definitions with filters (type, status, domain, visibility, search, tags, pagination)
get_definitionGet a single definition by type + name, optionally with YAML / runtime / refs
search_definitionsSearch definitions by keyword
list_modelsList AI models with optional filters
resolve_aliasResolve an alias (e.g. sonnet) to provider + modelId
validate_definitionValidate YAML without storing (accepts yaml or file_path)
render_definitionGet rendered markdown for a definition. output_path writes directly to a file

Definition management (P1)

ToolDescription
create_definitionCreate a new draft definition (accepts yaml or file_path)
update_definitionUpdate a draft definition. Smart version-up: if target version is published or doesn't exist and YAML is provided, automatically creates a new draft
publish_definitionPublish a draft definition
deprecate_definitionDeprecate with reason and optional successor
archive_definitionArchive a deprecated definition (terminal lifecycle state)
delete_definitionDelete a draft (published definitions cannot be deleted)

Composite workflows (P1)

ToolDescription
update_and_publishUpdate a draft and publish it in one call. Inherits smart version-up + create fallback from update_definition
batch_publishPublish up to 20 definition versions in one call. Continues on individual failures, returns both published and failed items

Versions & dependencies (P1)

ToolDescription
list_versionsList all versions of a definition
diff_versionsCompare two versions. format: sections (default), fields (structural + suggested bump), unified (git-style)
get_dependenciesForward dependency graph
get_dependentsReverse dependency graph
get_execution_statsExecution statistics for a definition version
list_forksList forks of a definition

Forks (P2)

ToolDescription
fork_definitionFork a definition
is_forkableCheck if a definition version can be forked
get_fork_lineageFork ancestry chain

Translation (P2)

ToolDescription
retranslate_definitionRetranslate with the latest translator version
upgrade_definitionUpgrade a definition from legacy format (accepts yaml or file_path)
get_translator_versionGet current translator version

Models & languages (P2)

ToolDescription
get_modelGet specific model details by provider + modelId
list_providersList AI providers
list_aliasesList all model aliases
list_languagesList supported definition languages (ADL, CDL, WDL, PDL)
get_languageGet a definition language with its current JSON Schema

Execution & users (P2)

ToolDescription
record_executionRecord a definition execution (idempotent)
get_userGet public user profile
batch_usersBatch user lookup (max 100)

Analytics (P3)

ToolDescription
get_effectivenessEffectiveness metrics for a definition: pass rate, scores, taxonomy, health score
get_healthHealth grade and issue profile for a definition
get_ecosystem_overviewEcosystem-wide analytics overview
get_lineageLineage graph for a definition (versions + forks as a tree)
get_evolutionVersion-over-version metrics with trend detection
get_translation_analyticsVersions grouped by translator version with aggregate metrics
compare_effectivenessCompare effectiveness across 2–5 definition versions side-by-side
get_diff_impactStructural diff combined with metric deltas between two versions

Session

ToolDescription
set_default_typeSet (or clear) a session-level default for the type parameter. When set, definition tools use this type unless explicitly overridden

Available resources

MCP resources provide read-only access to registry data via the registry:// URI scheme.

ResourceURIDescription
Definitionsregistry://definitionsPublished definitions (up to 100)
Modelsregistry://modelsAI model catalog
Definition typesregistry://definition-typesStatic list: agent, command, workflow, pipeline
Providersregistry://providersAI provider list
read_resource("registry://definitions")
read_resource("registry://models")
read_resource("registry://definition-types")

Rate limiting

This server uses mcp-secure-server with configuration tuned for typical harness usage patterns. Source of truth: src/index.ts (global) and src/config/tool-registry.ts (per-tool).

SettingValueNotes
Security levelbasic
Max requests/min120Global rate limit
Burst threshold15Requests within burst window
Burst window5000 ms
Automation detectionDisabledThe calling harness is trusted automation

Per-tool quotas are configured in src/config/tool-registry.ts. Read-heavy tools (list, get, search) allow up to 240 req/min. Write tools (create, update, publish) are 30–60 req/min.

Development

git clone git@github.com:Uluops/-uluops-registry-mcp.git
cd -uluops-registry-mcp
npm install
npm run build
npm test            # 348 tests
npm run typecheck
npm run lint

Requirements

  • Node.js: ≥ 18
  • Platform: Linux, macOS, or WSL2
  • Auth: UluOps API key (get one here)

License

MIT

Ver o original no GitHub

Bom para

Relacionados