Sprint 5 closed: MCP Server

Sprint 5 is closed.

The goal was to expose Meronq capabilities through MCP so AI assistants can use Meronq as a product tool layer — not only when developing Meronq itself. GitHub data and local memory from earlier sprints now ship through a dedicated product server with an explicit permission model.

What Sprint 5 delivered

Every item on the roadmap is checked off:

• MCP tool surface — handshake, scan, memory, GitHub, runtime, and git read tools
• Product server — apps/mcp-server v1.1.0 for any Meronq-enabled repository
• Shared server core — @meronq/server-core (handshake, permissions, runtime, CEM sync)
• Memory search — memory_search and memory_stats over SQLite
• Safety model — runtime and network gates via environment variables

Local MCP refactored onto @meronq/server-core (v1.15.0) while keeping dogfooding tools: git write, social distribution, and extended allowlists.

Product vs local MCP

Point either server at a repo with MERONQ_PROJECT_PATH (or MERONQ_PATH).

New package: @meronq/server-core

Shared logic extracted from local MCP:

Product MCP exposes 14 tools including memory_search, github_sync, project_build, and allowlisted commands. Git write stays off the product surface by design.

Permission model

MERONQ_ALLOW_RUNTIME=true   → build, test, install/dev allowlist
MERONQ_ALLOW_NETWORK=true   → GitHub API refresh (or set GITHUB_TOKEN)

Read-only git tools (git_status, git_diff) work without extra flags. See MCP server guide for Cursor configuration.

Memory search

memory_search queries entities in .meronq/local/memory.db with optional type filters. Access events are recorded when results are returned — aligned with ADR-0005.

# MCP: memory_search { "query": "github", "limit": 10 }

Sprint 6 — Skills and Workflows

Sprint 6 goal: introduce reusable procedural engineering knowledge — project.build, project.test, and adr.create as versioned Project Skills callable from MCP and CLI.

The product MCP surface is live; Sprint 6 adds deterministic workflows on top of it.

Follow along

• Roadmap — sprint plan
• MCP server setup
• Development blog
• GitHub: Meronq-dev/meronq

Sprint 4 connected GitHub. Sprint 5 makes project intelligence portable. Sprint 6 teaches assistants how to run repeatable engineering work.

Read the full post on meronq.pages.dev · Source on GitHub