---
title: Getting started
order: 1
---
# Getting started

Setting up takes about twenty minutes, once. You will need someone comfortable
pasting a link into Claude's settings. If that is not you, hand this page to
whoever does your computer things.

After it is set up, there is nothing to log into day to day. You answer
questions as they reach you, usually on your phone, and every agent working for
your business reads your answers before it acts.

## For whoever sets this up

You mount an organization; you do not log into an app. A mount is a live,
read-mostly view of the organization's knowledge at a named commit, plus the
run ledger and the decision queue. What your mount may do is decided by who
you are on it, and who you are comes from an invite code the Founder handed
you personally.

### From claude.ai (custom connector)

1. Settings → Connectors → add a custom connector pointing at
   `https://mainmind.app/mcp`.
2. Your assistant is redirected to the connect page; type your invite code
   once. The code maps to your name, role, and organization.
3. In any chat: call `boot` first. It returns the organization's entry
   documents (ORG.md, AUTHORITY.md), your role charter, and how to work from
   the mount.

### From Claude Code (plugin)

**Not yet available publicly.** The plugin lives in a private repository while
Mainmind is in early access, so the marketplace command below will not resolve
for you today. It is documented here so you know what the path will be, not so
you can run it now. Use the custom connector above, which works.

```
/plugin marketplace add codeyogi911/mainmind
/plugin install mainmind
```

The plugin ships transport and mount discipline and no secrets. The
`mainmind-boot` skill enforces the discipline: boot before answering, cite
paths and the projection commit, open a run before real work.

### From anything with an HTTP client

Every tool has a plain-HTTP twin (see [HTTP API](/docs/http-api)). A cron
job, a shell script, or an agent harness with no MCP support drives the
identical contract:

```
curl -s https://mainmind.app/api/health
curl -s https://mainmind.app/api/surface
```

### The working discipline

Whatever the transport, the shape of good work is the same:

1. `boot`, then obey what it returns, those documents outrank anything you
   remember.
2. Route tasks through `find_process`; read the Process with `read_node`
   before acting; cite paths and the commit for every material claim.
3. Open a run (`run_start`) before real work, heartbeat as you move, finish
   it when done. That is what makes you visible to the team.
4. A decision that belongs to the Founder goes through `ask_founder`: one
   yes/no question, what becomes true, evidence attached. Never split one
   decision into many asks.