Reported issues for worklore

Pod holds 6 of 6 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 worklore.

Most discussed

Port to MCP spec 2026-07-28 (per-request version, server/discover, UnsupportedProtocolVersionError)

What

Port the MCP server from the handshake-era revision it implements today (2025-06-18) to the current spec revision, 2026-07-28.

Why now

Found while connecting the MCP Inspector to https://worklore.dev/mcp: the Inspector displayed the negotiated protocol as MCP 2025-11-25, which the server had no business agreeing to.

The immediate defect — initialize echoed back any protocolVersion the client sent, including 2099-01-01 and banana — is already fixed: the…

Read the thread · 2026-09-23 · open · 7 comments

Check registry + directory discoverability (tomorrow), then trigger the article

Published io.github.worklore/worklore to the official MCP Registry on 2026-09-15 (issue #13). Verify it has propagated:

• Official registry search returns it: curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=worklore" (already live at publish time — recheck stays green).
• It appears in the human-facing aggregator directories that sync the official registry: mcp.so, Glama, PulseMCP, Smithery (search "worklore"). These usually index within a day or two.
• Note…

Read the thread · 2026-09-15 · closed · 4 comments

[16] (optional) Submit a ChatGPT app via OpenAI Developer Platform

(optional) Submit worklore as a public ChatGPT App in the directory — broader reach than the personal Developer-Mode connector. Separate ecosystem; do after Registry (#13 ✓ done) if worth it.

Where to start (registration)

• Prerequisite — verify identity/business: https://platform.openai.com/settings/organization/general
• Submission flow (portal steps, review, publishing): https://developers.openai.com/plugins/deploy/submission
• Guidelines:…

Read the thread · 2026-09-09 · open · 4 comments

publish_story write tool (v2)

The natural v2 write tool: an agent can publish a worklore story on the human's behalf over MCP (after showing the full draft and getting explicit approval — mandated in the tool description).

Shipped 2026-09-16.

• publish_story tool on worklore.dev/mcp: takes markdown OR (title/narrative/reproduce/tags/type/stack); assembles frontmatter, reuses the API's injection lint + frontmatter validation.
• Write annotations: readOnlyHint:false, openWorldHint:true,…

Read the thread · 2026-09-16 · closed · 1 comment

[17] Expose /mcp at worklore.dev (CloudFront behavior)

The endpoint works on the API Gateway URL but worklore.dev/mcp 403s — CloudFront only proxies /v1/*. Add a cache behavior routing /mcp to the API origin so the connector has a clean, branded URL.

• Add CloudFront behavior: path /mcp -> API Gateway origin (no cache, forward POST + headers)
• Verify POST https://worklore.dev/mcp returns the JSON-RPC result

Acceptance: worklore.dev/mcp speaks MCP. May need Valentina for the CloudFront change if it is out of scope for the…

Read the thread · 2026-09-10 · closed · 1 comment

[1] Confirm the v1 tool set

Decide the v1 tools before building. Read-first, safe, showcase the tier differentiator.

• check_capability(url|text) — skill-xray tier + findings
• get_story(slug) — contract + tier/findings (disclosure at the API boundary)
• search_stories(query)
• suggest_for_project(context)

Defer to v2: publish_story, report_reproduction.

Done when: you confirm/edit this list in a comment. Then #2 starts.

Read the thread · 2026-09-09 · closed · 0 comments

Most recent

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