Project Setup

Connect a repository in one prompt.

Once the ContextHarbor MCP server is connected to your agent, you do not hand-edit config files. Ask in plain language and the agent drives the setup tools, writing each file to its place in the repository.

Request an evaluation trial See integrations

In the Web portal

The Project Setup wizard walks the same three steps.

ContextHarbor Project Setup, step 1: choosing the project and editor or harness from two dropdowns — Step 1 — pick the project and your editor or harness. Everything downstream is rendered for that pair.

Automatic harness setup

"Set up the ContextHarbor harness for project SEG-PACE in this repo."

The agent calls setup_agent_harness and writes every file it returns, rendered for your project with target paths and merge modes.

Skill file

Focused retrieval guidance — query rewriting, doc-type routing, scoping — written to the harness skill path.

AGENTS.md block

A managed block merged into the repository's AGENTS.md so any compatible agent knows the project and how to query it.

CLAUDE.md block + hook

For Claude Code, a CLAUDE.md block between managed markers plus a memory-capture Stop hook merged into settings.json.

Other harnesses — Cursor, OpenCode, Codex, and generic MCP clients — receive the skill file and the AGENTS.md block. setup_harness returns just the Claude Code Stop hook fragment when that is all you need.

ContextHarbor Project Setup, step 2: a single copyable install prompt that tells a connected agent to call setup_agent_harness and index the repo — Step 2 — copy one install prompt into a connected agent. It calls `setup_agent_harness`, writes each file, then indexes the repository.

Index the code

"Index this repository into the ContextHarbor code graph."

1. Agent fetches the scriptIt calls setup_code_graph, writes the returned POSIX script, and runs it. Auth reuses the harness MCP key — no key prompt.

2. Pick the branchThe first run per repository asks which branch to index — the one you deploy from.

3. Verify and keep freshConfirm with get_code_brief; reruns auto-delta from the last indexed commit, or run ch code sync.

The Web portal Project Setup page generates the same artifacts.

Project SetupAt /setup/project, pick a project and harness and copy the skill file, AGENTS.md block, and code-graph script.

MCP SetupAt /setup/mcp, generate the per-harness MCP server configuration with your key embedded, when the server base URL is set in admin Settings.

Same output, no agentThe portal renders exactly what setup_agent_harness would write, for teams that add the files by hand.

Project Setup

Stop wiring context by hand in every repository.

Tell us which repositories and coding tools your team works in.

Request an evaluation trial Explore memories

Pricing depends on deployment, integration, and support requirements.