io.github.worklore/worklore
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided description
Search worklore stories and x-ray any skill or story capability tier (T0-T4) before you run it.
Summary by lookupd
Searches and retrieves community stories, checks skills for capability tiers, and records reproductions and edit suggestions.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http worklore https://worklore.dev/mcp
Codex, remote (streamable-http)
codex mcp add worklore --url https://worklore.dev/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"worklore": {
"url": "https://worklore.dev/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (10 tools)
Publisher-provided text
check_capabilityDisclose what an agent Skill or worklore story CAN DO before you run it: a capability tier T0-T4 bound to a content sha256, with findings that carry file:line eget_storyFetch one worklore story by slug — its full markdown (narrative + the 'Reproduce this' contract your agent would run) WITH its capability disclosure attached (tsearch_storiesSearch worklore stories by keyword across title, summary, tags and stack. Returns matches with their capability tier.explore_keywordsThe worklore keyword map: every story tag with its story count, in four editorial groups (tools and agents, building blocks, practices, off the clock), plus thesuggest_for_projectGiven a short description of the current project (stack, what you're building, recent problems), suggest up to 3 worklore stories worth reproducing here, with wreport_reproductionCall this right after you apply a worklore story's steps to the user's own task, to record the reproduction (attributed to the signed-in account). Use an honestreport_checkRecord the result of a story's read-only 'Check if this applies to you' section, run in the user's own project (attributed to the signed-in account). Run ONLY tpublish_storyPublish a NEW worklore story as the signed-in account. worklore stories are PUBLIC and honest, so before you call this you MUST show the human the complete drafedit_storyRevise a worklore story the signed-in account PUBLISHED — only its author can edit it. Call get_story first, then show the human a before/after diff of your chasuggest_editPropose a revision of a worklore story written by SOMEONE ELSE, for its author to accept or decline — worklore's pull request. Use it when, while reproducing a
Details
- Version: 0.9.0
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 549 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/worklore/worklore-mcp
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.github.worklore/worklore)
- 62071 servers
- Last crawl: 2026-11-11T16:39:06.253Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp