Add it to Claude Code
claude mcp add --transport http cleanslice https://mcp.cleanslice.org/mcpMake your agent remember this setup
cleanslice's config, env vars, and the gotchas you hit — recalled in every future Claude Code, Cursor, and Codex session.
npx conare@latestFree · one command · indexes the sessions already on disk. Set up in the browser instead →
What it does
- Provides AI agents with direct access to CleanSlice architecture documentation
- Enables searching for implementation details and architectural constraints
- Supports retrieval of full documentation files for deep context
- Integrates with Claude Code and Cursor for automated architectural guidance
Tools 4
get-startedLoads the core architecture rules for CleanSlice.list-categoriesLists available documentation areas within the CleanSlice architecture.searchSearches documentation for task-relevant queries.read-docReads the full content of a specific documentation file.Try it
Original README from CleanSlice/mcp
CleanSlice MCP Server
MCP (Model Context Protocol) server that gives AI coding agents access to the CleanSlice architecture documentation. Connect it to Claude, Cursor, Windsurf, or any MCP-compatible client so the AI knows how to build apps using CleanSlice conventions.
Installation
<details> <summary><b>Install in Claude Code</b></summary>Run this command. See Claude Code MCP docs for more info.
claude mcp add --scope user --transport http cleanslice https://mcp.cleanslice.org/mcp
Remove
--scope userto install for the current project only.
Tip: enforce MCP usage with CLAUDE.md
To make sure Claude Code always consults the CleanSlice MCP before writing any code, add the following to your project's CLAUDE.md:
## CleanSlice MCP — Required
Before writing or modifying any code you MUST consult the CleanSlice MCP:
1. Call `get-started` to load the core architecture rules.
2. Call `list-categories` to see available documentation areas.
3. Call `search` with at least 2 task-relevant queries covering:
(a) core implementation details for the feature you are building,
(b) edge cases, constraints, or standards that apply.
4. Call `read-doc` to read the full document when search snippets aren't enough.
Do NOT guess conventions — always verify against MCP results first.
This ensures the agent reads CleanSlice docs at the start of every task, not after the fact.
Optional: add a Stop hook as a safety net
To catch cases where the agent skips the MCP despite the CLAUDE.md instruction, add this to .claude/settings.json:
{
"hooks": {
"Stop": [
{
"hooks": [
{
"type": "agent",
"timeout": 180,
"prompt": "You are a verification subagent. Your job: ensure the main Claude Code agent used the `cleanslice` MCP knowledge sufficiently and did not guess.
Context JSON:
$ARGUMENTS
Verification requirements:
1) Identify what the user asked for (deliverables + constraints) from the conversation/transcript in $ARGUMENTS.
2) Verify the agent consulted the `cleanslice` MCP server for relevant knowledge BEFORE finalizing:
- Must call `cleanslice` \"get-started\" at least once (or equivalent) to confirm the server's purpose and usage.
- Must call \"list-categories\" to understand the available knowledge areas.
- Must call \"search\" with task-relevant queries (at least 2 searches) covering: (a) core implementation details, (b) edge cases / constraints.
- May call \"read-doc\" to get full document content when search snippets are insufficient.
3) Validate coverage:
- If any required category is relevant but not checked, fail.
- If answers include specifics that are not supported by MCP results, fail.
4) Output STRICT JSON only:
- If everything is verified: {\"ok\": true}
- If anything is missing/unsupported: {\"ok\": false, \"reason\": \"What is missing + exact MCP calls the main agent must run next (e.g., run list-categories, then search for X/Y, then update the solution).\"}
Important:
- `cleanslice` tools will appear as MCP tools. Use whatever exact tool names are available in this environment (they follow the mcp__<server>__<tool> naming pattern).
- Do not allow stopping until MCP-backed evidence is sufficient."
}
]
}
]
}
}
Go to: Settings -> Cursor Settings -> MCP -> Add new global MCP server
Paste the following into your Cursor ~/.cursor/mcp.json file. You may also install in a specific project by creating .cursor/mcp.json in your project folder. See Cursor MCP docs for more info.
{
"mcpServers": {
"cleanslice": {
"type": "http",
"url": "https://mcp.cleanslice.org/mcp"
}
}
}
Tip: enforce MCP usage with a Cursor rule
Create .cursor/rules/cleanslice.mdc in your project to make Cursor always consult the MCP before writing code:
---
description: CleanSlice architecture rules
globs: **/*.{ts,vue,prisma}
alwaysApply: true
---
## CleanSlice MCP — Required
Before writing or modifying any code you MUST consult the CleanSlice MCP:
1. Call `get-started` to load the core architecture rules.
2. Call `list-categories` to see available documentation areas.
3. Call `search` with at least 2 task-relevant queries covering:
(a) core implementation details for the feature you are building,
(b) edge cases, constraints, or standards that apply.
4. Call `read-doc` to read the full document when search snippets aren't enough.
Do NOT guess conventions — always verify against MCP results fir