liblib-mcp-server

⚠ Stale — 197d ago

Provides an MCP server that dynamically exposes Liblib/ComfyUI workflows as MCP Tools, alongside a management UI and REST APIs for multi-tenant workflow and credential management.

Evaluated Apr 04, 2026 (197d ago)

Repo ↗ DevTools mcp comfyui liblib go multi-tenant api workflow-automation self-hosted

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

README claims AES-256-GCM encryption for stored API keys (improves secret-at-rest safety) and JWT/Bearer auth for requests. However, TLS is only described as 'supports HTTPS deployment' rather than enforced, and there is no evidence of fine-grained scopes/roles, rate-limit controls, CSRF protections (for UI), or detailed security error handling. Dependency list is minimal but no vulnerability/SBOM evidence is provided.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

Self-hosting a lightweight MCP gateway for Liblib/ComfyUI workflows with per-user isolation and an accompanying admin UI.

Avoid When

When you need a fully specified OpenAPI spec, SDKs, or clearly documented operational guarantees (SLA, rate-limit headers, error codes).

Use Cases

• Connect an MCP-capable client (e.g., IDE assistants) to Liblib ComfyUI workflows as callable tools
• Manage Liblib API credentials and map workflow UUIDs to MCP tools per tenant/user
• Automate workflow execution with dynamic parameter parsing/validation

Not For

• Highly regulated environments requiring formally verified compliance controls (not evidenced in provided materials)
• Public internet deployments without additional infrastructure hardening (rate limiting, WAF, network controls) not described in README

Interface

REST API

Yes

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Webhooks

Authentication

Methods: JWT Bearer token (for management API)

OAuth: No Scopes: No

README describes login to obtain a JWT token and Bearer auth for API routes and MCP auth token usage; does not mention fine-grained scopes/roles.

Pricing

Free tier: No

Requires CC: No

Self-hosted open-source project; no commercial pricing described.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ No explicit documentation for MCP tool list/discovery behavior beyond general statements; agent may need to probe tools at runtime.
⚠ MCP authentication relies on a Bearer token passed as MCP_AUTH_TOKEN; ensure token is accepted for /mcp tool calls.
⚠ Rate limits are not documented; agents may need to implement conservative request pacing.

Alternatives

MCP adapters built directly on top of Liblib APIs plus a separate workflow/credentials store Use mark3labs/mcp-go directly with a custom thin wrapper (if you need tighter control) Build a REST-only integration to Liblib/ComfyUI workflows and skip MCP

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for liblib-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.