
Repository guidance
Keep the durable rule in CLAUDE.md.
Add one compact rule: search the corpus before generating recurring primitives, reject weak or unknown-license matches, and run repository tests after every retrieval.
Connection status
Supported now: scoped HTTP API key. Use a local tool or your own MCP adapter; no one-click public Claude Code package is claimed here.
Setup
A retrieval-first connection in five steps.
- 01
Create a scoped, revocable Moresq API key from the Corpus workspace.
- 02
Expose corpus.search and corpus.retrieve to Claude Code through a local tool or MCP adapter.
- 03
Keep stable security and repository rules in CLAUDE.md.
- 04
Search metadata with the language, framework and critical constraint.
- 05
Retrieve only a strong match, then preserve the proof receipt and run tests.
export MORESQ_API_KEY="md_..."
export MORESQ_PROJECT="6de3..."
curl -X POST https://data.moresq.com/data/v1/functions/corpus.search \
-H "Content-Type: application/json" \
-H "X-API-Key: $MORESQ_API_KEY" \
-H "X-Project: $MORESQ_PROJECT" \
-d '{"q":"retry with exponential backoff","limit":5}'Frequently asked questions
Does Moresq replace CLAUDE.md?
No. CLAUDE.md is the right place for compact, stable repository rules. Moresq stores detailed implementation cards and evidence that should be retrieved only for relevant tasks.
Is there a public one-click Claude Code MCP package?
Not yet. The current supported connection is the Moresq HTTP API through a scoped key, either called by a local tool or wrapped by your own MCP adapter.
What should Claude Code retrieve first?
Start with repeated, bounded primitives such as validation, pagination, retries, webhook verification and deployment diagnostics.