pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for Huly MCP by dearlordylord

Pod holds 19 of 99 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to Huly MCP by dearlordylord.

Most discussed

Effect 4: Migrate boards, cards, inventory, recruiting, leads, and support

Parent

#209

What to build

Restore the specialist boards, inventory, recruiting, lead, and support workflows under Effect 4.

Acceptance criteria

  • Migrate owned schemas, parsers, tagged errors, service consumers, operations, adapters, MCP and CLI exposure, and adjacent tests.
  • Preserve board and card relationships, inventory media and templates, recruiting applicants and schedules, lead state, support behavior, descriptions, and authored schema constraints.
  • Prove repr

Read the thread · 2026-08-12 · closed · 9 comments

Feature: Boards, inventory, products, tags, templates, views, and preferences

gpt 55

gpt 55 note - 2026-06-18

Board core MCP coverage landed in PR #130 and is now merged.

Covered in this slice:

  • Board discovery and safe board writes: list/get/create/update/archive/unarchive board.
  • Board card discovery and safe card writes: list/get/create/update/archive/unarchive/delete archived card.
  • Board card fields covered: title, markdown description, status, kind, assignee, members, location, cover, startDate, dueDate, archived state.
  • Board/card domain errors and MCP in

Read the thread · 2026-06-07 · closed · 9 comments

edit_document and create_document: raw markdown breaks Huly collaborative editor

Problem

When creating or editing documents via MCP, the content is written as raw markdown to the database. Huly's UI reads documents from a collaborative document (via the collaborator service) using ProseMirror JSON format. Without calling uploadMarkup through the collaborator service, the collaborative document is never properly initialized.

This mirrors the milestone issue (#17) which was fixed in PR #18 for milestones, but documents haven't received the same treatment.

S

Read the thread · 2026-06-03 · closed · external user · 8 comments

Effect 4: Migrate the operation registry and prove complete schema parity

Parent

#209

What to build

Make the complete MCP operation and resource catalog constructible under Effect 4 and prove that its public schemas and discovery behavior still match the Effect 3 oracle.

Acceptance criteria

  • Register all 522 operations and the complete resource surface with their migrated input and output schemas, descriptions, annotations, errors, and toolset metadata.
  • Route every production Schema-to-public-JSON-Schema conversion through the central Draft-07

Read the thread · 2026-08-12 · closed · 7 comments

Effect 4: Migrate administration and extension domains

Parent

#209

What to build

Restore administrative, discovery, search, preference, tagging, view, custom-field, deletion, and generic relation behavior under Effect 4.

Acceptance criteria

  • Own security, model and sequence administration, SDK discovery, search, preferences, tags and tag categories, views, custom fields, deletion, associations, generic relations, and workbench behavior.
  • Migrate all owned schemas, parsers, tagged errors, service consumers, operations, adapter

Read the thread · 2026-08-12 · closed · 7 comments

[Bug]: npx execution fails with EUNSUPPORTEDPROTOCOL due to unresolved workspace: dependencies

Description

When attempting to run the package via npx, the execution immediately fails because npm encounters an unresolved workspace: protocol in the dependency tree.

It appears that @firfi/huly-mcp (or its @hcengineering/* dependencies) was published to the public npm registry without replacing the monorepo workspace: protocols with actual semantic version numbers in the published package.json.

Steps to Reproduce

Run the following command in any standard npm environment:

Read the thread · 2026-03-27 · closed · external user · 5 comments

Effect 4: Prove CLI documentation and packed-artifact parity

Parent

#209

What to build

Make the shipped CLI package and generated agent-facing documentation demonstrably equivalent to the Effect 3 baseline.

Acceptance criteria

  • Regenerate and verify README and Agent Skill command documentation from catalog-owned metadata.
  • Compare root, group, and leaf help snapshots and the complete route and registry parity contract against the baseline.
  • Pack the CLI and verify installation, version output, help, representative structured-i

Read the thread · 2026-08-12 · closed · 4 comments

list_comments crashes with 'Connection error' when issue has MarkupContent-object comments

Bug

list_comments returns Connection error while communicating with Huly when an issue has comments whose message field is a MarkupContent object (rather than a ProseMirror JSON string).

Root cause

optionalMarkupToMarkdown (in dist/index.cjs) assumes markup is always a string:

function optionalMarkupToMarkdown(markup, urls, fallback = "") {
  return markup === null || markup === void 0 ? fallback : markupToMarkdownString(markup, urls);
}

`markupToMarkdownStrin

Read the thread · 2026-08-27 · closed · external user · 3 comments

Most recent

Certify and publish the breaking Effect AI release

What to build

Certify the breaking Effect AI MCP server as a releasable Huly MCP package after the in-place migration. Exercise the real built artifact over both transports and against local Huly, record the deliberately changed protocol behavior, update the behavioral oracle and user-facing guidance, and prepare the breaking release metadata.

Certification owns fixing migration defects it exposes; it must not restore the deleted Promise SDK or MCP 2026-07-28 compatibility path.

Accep

Read the thread · 2026-08-18 · closed · 1 comment

Replace the MCP SDK with Effect AI in place

What to build

Replace the Promise-based MCP SDK edge with the project-pinned Effect AI MCP server in one breaking, in-place migration. Tools, resources, stdio, and HTTP must move together, and the old SDK implementation must be deleted rather than retained as a compatibility path.

Build one generic adapter over the existing tool and operation registries so the complete Huly catalog moves without duplicating declarations or converting tools individually. Preserve Huly-owned behavior includin

Read the thread · 2026-08-18 · closed · 1 comment

Prevent orphaned stdio MCP processes with bounded shutdown

Problem Statement

When a Codex or other stdio MCP client exits without sending SIGTERM, Huly MCP can survive as a PID-1 orphan because stdin EOF is not treated as process-owner departure in every supported configuration. During the observed incident, 24 orphaned Huly MCP processes contributed to roughly 9 GiB of combined RSS and swap across 61 processes.

Shutdown is also not bounded as a whole. In-flight request draining, SDK wire close, telemetry flush, and process-scoped Huly client relea

Read the thread · 2026-08-12 · closed · 0 comments

Effect 4: Certify local Huly integration and prepare release evidence

Parent

#209

What to build

Prove the Effect 4 build against a real local Huly deployment and leave complete parity and release evidence for merging the integration branch.

Acceptance criteria

  • Run the documented full local-Huly integration suite from the container with environment loading and the localhost-to-host.docker.internal URL rewrite.
  • Run stdio MCP, HTTP environment authentication, HTTP header authentication, tool-scope, and packed CLI integration paths against lo

Read the thread · 2026-08-12 · closed · 2 comments

Effect 4: Certify MCP and CLI artifacts on Node 22 and 24

Parent

#209

What to build

Prove clean consumers can install and run both published artifacts on every supported Node line with a reproducible dependency and bundle closure.

Acceptance criteria

  • Perform clean pnpm installs and native tool startup on supported Node 22 and Node 24 lines in the package-smoke matrix.
  • Build, pack, install, and execute the MCP and CLI artifacts in clean consumers on both supported Node lines.
  • Verify embedded version behavior, package cont

Read the thread · 2026-08-12 · closed · 2 comments

Effect 4: Rebuild the HTTP transport

Parent

#209

What to build

Restore the HTTP MCP endpoint on the Effect 4 router and server model while preserving authentication, isolation, concurrency, and lifecycle behavior.

Acceptance criteria

  • Reconstruct routing and serving using exact rc.108 HTTP APIs rather than treating the migration as a symbol rename.
  • Prove bind, port-zero allocation, listen readiness, close, interruption, startup failure, and graceful shutdown behavior.
  • Preserve malformed JSON-RPC handl

Read the thread · 2026-08-12 · closed · 2 comments

Effect 4: Migrate the complete CLI framework and route behavior

Parent

#209

What to build

Restore the full generated CLI on Effect 4 while preserving route coverage, raw argument semantics, help, execution, and exactly-once error rendering.

Acceptance criteria

  • Use the Effect 4 unstable CLI and Node services APIs for command construction and execution.
  • Make the application catalog the source of truth for root, group, and leaf routes, descriptions, options, arguments, and help rather than framework command-tree introspection.
  • Pr

Read the thread · 2026-08-12 · closed · 2 comments

Effect 4: Migrate the MCP server and stdio lifecycle

Parent

#209

What to build

Restore the production MCP server and stdio transport under Effect 4 with correct request scopes, concurrency, interruption, and shutdown.

Acceptance criteria

  • Migrate server construction, protocol handlers, resource handlers, stdio wiring, and their service and layer dependencies to Effect 4.
  • Migrate the concentrated server lifecycle and concurrency tests to Effect 4 test, clock, fiber, and synchronization semantics without mocks or real-time s

Read the thread · 2026-08-12 · closed · 3 comments

Effect 4: Migrate contacts, collaborators, organizations, comments, and external channels

Parent

#209

What to build

Restore people, organization, collaboration, commenting, and external-channel operations under Effect 4.

Acceptance criteria

  • Migrate owned schemas, parsers, tagged errors, service consumers, operations, Huly adapters, registrations, catalog metadata, and adjacent tests.
  • Preserve person and organization resolution, collaborator projections, comment attachment behavior, external-channel identity rules, descriptions, and public schemas.
  • Prov

Read the thread · 2026-08-12 · closed · 3 comments

Effect 4: Migrate documents, drive, storage, and attachments

Parent

#209

What to build

Restore document, file, storage, and attachment operations under Effect 4 without changing serialized contracts or resource ownership.

Acceptance criteria

  • Migrate owned schemas, parsers, tagged errors, service consumers, operations, adapters, registrations, catalog metadata, and adjacent tests.
  • Preserve rich content, metadata, upload and download inputs, attachment association, storage errors, descriptions, output encoding, and authored JSON Sc

Read the thread · 2026-08-12 · closed · 2 comments

Effect 4: Migrate planner, workspace, spaces, processes, tasks, time, and test management

Parent

#209

What to build

Restore planning, workspace structure, process execution, task, time, and test-management behavior under Effect 4.

Acceptance criteria

  • Migrate every owned boundary schema, parser, tagged error, public JSON Schema consumer, service-shape consumer, operation, adapter, MCP and CLI exposure, and adjacent test.
  • Preserve workspace and space resolution, planner relationships, process and workflow state, time semantics, task projections, and test-manag

Read the thread · 2026-08-12 · closed · 3 comments

The remaining reports are on the project's issue tracker.