# Start with your coding agent

> Connects Claude Code, Cursor or another coding agent to Mindset, so it builds, tests and changes your agents for you.

**Skill for your coding agent:** [`mindset-embed/SKILL.md`](https://docs.mindset.ai/skills/mindset-embed/SKILL.md)

**Skill for your coding agent:** [`mindset-uiless/SKILL.md`](https://docs.mindset.ai/skills/mindset-uiless/SKILL.md)

Your coding agent builds Mindset agents through the `mindset-admin` MCP server, and the Mindset skills tell it how to do each job. It changes your code and the agent's files in the same session, and the plumbing stays in Mindset, so none of it becomes code your team maintains. See [Why Mindset is MCP first](https://docs.mindset.ai/docs/how-mindset-fits-together#why-mindset-is-mcp-first). Every Builders guide starts with a prompt to hand it.

## Ask your coding agent

```
Connect this project to Mindset's admin MCP server, then tell me which org and environment you're in and list my agents.
```

Skill: [mindset-mcp](https://docs.mindset.ai/skills/mindset-mcp/SKILL.md)

## Set it up

### 1. Open Settings → Systems

Under **Connect an AI client**, choose **For administrators**.

![Settings → Systems, with For administrators chosen and the Claude Code prompt below.](https://docs.mindset.ai/images/docs/studio/settings-systems.png)

### 2. Pick your tool

Pick the tool you work in: **Claude Code**, **Cursor**, **Copilot (VS Code)**, **Claude Desktop** or **Claude.ai**.

### 3. Paste the prompt

Copy the prompt and paste it into your client. For Claude Code, it runs:

```sh
claude mcp add --transport http --scope project mindset-admin https://<your Mindset host>/api/v1/orgs/<org>/envs/<environment>/mcp
```

It also adds a short "Using Mindset" note to the project's `CLAUDE.md`, so the agent knows what Mindset is next session.

### 4. Sign in

In Claude Code, run `/mcp`, pick `mindset-admin` and sign in with your Mindset account in the browser. There's no key to paste.

### 5. Check it works

Ask your client "list my Mindset agents".

The address names one [environment](https://docs.mindset.ai/docs/environments): the one chosen in the nav switcher when you copied it. Switch first if you want a different one.

Only org admins can use `mindset-admin`. Anyone else gets "not found", and calls published agents through the members' server instead: see [Use your agents from AI clients](https://docs.mindset.ai/docs/use-your-agents-from-claude-and-other-ai-clients). [MCP tools](https://docs.mindset.ai/docs/mcp-tools) lists every tool, and every call is checked against your admin permissions.

## Give it the skills

A skill is a SKILL.md file your coding agent loads when a task needs it. Start with the one that installs the MCP server and explains orgs and environments:

**Skill for your coding agent:** [`mindset-mcp/SKILL.md`](https://docs.mindset.ai/skills/mindset-mcp/SKILL.md)

[Skills](https://docs.mindset.ai/skills) lists one skill per job, and each guide names the skill its prompt uses. Every docs page is also Markdown: add `.md` to its URL. `/llms.txt` indexes every page, and `/llms-full.txt` holds them all in one file.

> **Info:** Your coding agent works under the same [compliance rules](https://docs.mindset.ai/docs/compliance) as the rest of your team. It never sees a credential and can't approve a write. [Work with the MCP server](https://docs.mindset.ai/docs/work-with-the-mcp-server) lists what stays with a person.

## Done when

Your client names the org and environment it's in and lists your agents, and no key ever appeared in the conversation.