Cursor setup guide

Extend Cursor codebase context with governed implementation memory

Cursor already understands the active codebase. Moresq adds a different layer: implementation cards from prior approved work, with license, trust and receipt metadata that can be searched without indexing private source into a public catalogue.

Cursor retrieving one proof-backed implementation before changing a repository.
The agent receives compact metadata first and full code only after the retrieval gate. Open image.

Repository guidance

Keep the durable rule in .cursor/rules.

Keep project conventions in Cursor rules and route cross-project reuse through a local API tool. Require explicit review for auth, billing, persistence and shell-execution artifacts.

Connection status

Supported now: scoped HTTP API key. Use a local tool or your own MCP adapter; no one-click public Cursor package is claimed here.

Setup

A retrieval-first connection in five steps.

  1. 01

    Generate a scoped Moresq key from the authenticated workspace.

  2. 02

    Connect the HTTP API through a local command, extension task or MCP adapter.

  3. 03

    Keep repository-specific conventions in .cursor/rules.

  4. 04

    Search the corpus only for reusable patterns that the active codebase does not already provide.

  5. 05

    Apply with a proof receipt, inspect the diff and run the project test suite.

moresq-corpus.http
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

How is Moresq different from Cursor codebase indexing?

Codebase indexing finds what already exists in the active project. Moresq retrieves reusable implementation patterns and evidence across prior work and approved catalogues.

Does Moresq send my private repository to a public catalogue?

No. Public catalogue metadata and tenant-scoped private candidates are separate surfaces. Depositing a reusable artifact requires an explicit workflow and provenance.

Can Cursor use Moresq through MCP?

Yes through an MCP adapter that calls the current HTTP API. Moresq does not currently advertise a one-click public MCP package.

Create a scoped key, then let Cursor search before it generates.

Create an agent key