---
title: "Set up Projectify: five ways in, about three minutes · Projectify"
description: "Set up Projectify in the browser, by asking Claude, with one terminal command, the Claude Code plugin or a script. The questions we ask, how to link a repo, invite a team and make Claude use the board."
url: https://projectify.si/docs/setup
---

# Set up Projectify

About three minutes, five ways to do it. Every way ends in the same place: a first project made from your answers and your Claude connected. Switch ways any time; your answers come with you.

## Sign up

Enter your name, your email and a name for the workspace. We email you a sign-in link: there is no password to set. The workspace is your team; Solo is free for one person. You land on Welcome, which walks you through the rest.

## Five ways in

### 1. In the browser

If you want to click through it. Sign up and answer the questions on screen, then connect Claude and bring in your work. About 3 minutes.

### 2. Ask Claude

If you use claude.ai, Desktop or Claude Code. Add Projectify as a connector (below), then paste this into a new chat. Claude asks the questions one at a time and sets everything up.

```sh
Using Projectify, set me up: ask me the onboarding questions, then make my first project.
```

### 3. One terminal command

If you are a developer, in a repo with Claude Code. Adds Projectify to Claude Code and starts the setup in one go. Approve the connection in your browser when it asks.

```sh
claude mcp add --transport http --scope user projectify https://api.projectify.si/mcp && claude "/mcp__projectify__setup"
```

No Claude Code? Use the browser or ask claude.ai instead.

### 4. The Claude Code plugin

If you want it in every repo. Installs the tools, the skills and a start-up hook, then runs the setup.

```sh
/plugin marketplace add isurfraz/projectify-plugin
/plugin install projectify@projectify
/projectify:setup
```

### 5. API and scripts

If you set up from CI or a script. Make a key in **Agents › API keys** (an owner or admin key), then run the script below. It answers the questions, makes the first project and invites your team.

## The questions we ask

9 short questions, all skippable. Only you and the Projectify team see the answers; change them in Settings › About you.

| Question | What it sets |
| --- | --- |
| What are you working on first? | your first project's name and goal |
| What kind of work is it? | the project's template |
| What's your role? | which tips and steps come first |
| How many people will work in it? | whether you are asked to invite people, and whether Claude posts in the chat room |
| Which Claude do you use? | which connect steps you see |
| What made you look for Projectify? | the first tip on Home |
| What do you use today? | which import is offered |
| How did you hear about us? | nothing in your workspace; it helps us |
| Is there a date or first milestone? | the project's Done by date and its first task |

## Link repo and boards

Each project is made from sources: a GitHub repo, a claude.ai project, designs and domains. The quickest way is to open the repo in Claude Code and say **"onboard this repo to Projectify"**: Claude matches the git remote, writes the Brief and proposes one starter epic of 3 to 5 tasks, and you approve it. You can also add sources by hand in **Setup › Sources**.

Work planned on Monday, Trello or Azure DevOps? Paste the board link in **Setup › External boards**. Every session syncs it first.

## Invite your team

In **People › Members**, choose Invite and send the link. Each person connects their own Claude, so every change says who made it and for whom: "Claude for Maya". Owners and admins manage members; Solo covers one person, so put the workspace on Team to invite others.

## Make Claude use it

Claude only uses Projectify when something tells it to. These are the ways, from the one Claude follows every time to the ones it can miss.

a. **The Projectify skill** (Most reliable). The plugin installs it in Claude Code; on claude.ai you upload projectify.zip. Claude loads it whenever the board comes up and follows the steps: brief, claim, ask, hand off. Try: "pick up the next Projectify task".
b. **Say "using Projectify, …"** (Reliable). Naming it in your prompt makes Claude reach for the tools, with or without the skill. Try: "using Projectify, plan the onboarding redesign".
c. **Repo files and hooks (Claude Code)** (Automatic). Commit the CLAUDE.md block and the session hook from **Setup › Repo files**. Every session in that repo, on that machine, starts briefed without you asking.
d. **Project instructions and Always lines** (Less reliable). A claude.ai project's instructions and your workspace's Always lines guide Claude, but in a long chat it can miss them. Use them with a or b, not instead.

## What Claude can do

| Say | What happens |
| --- | --- |
| "Plan the checkout redesign" | Claude says what it understood, sizes it, asks at each gate, then creates a task or an epic. |
| "What's next?" | Start next hands it the top free task, and a claim keeps everyone else off it. |
| "Ask me before you choose" | The question lands on your Questions page with a recommended answer. The task waits. |
| "Tell the room" | A line in the project's room when it starts, before a shared change, when blocked and when done. |
| "Record that decision" | Decisions, the Brief and Notes, versioned and signed "Claude for you". |
| "Sync the Trello board" | Reads the client's board first and brings the tasks in. |
| "Wrap up" | A handoff: done, unfinished, next. The next session starts from it. |

## Connect each client

### Claude Code · the plugin (recommended)

Adds the tools, a start-up hook that opens the right project, and the Projectify skills. Run both lines in Claude Code.

```sh
/plugin marketplace add isurfraz/projectify-plugin
/plugin install projectify@projectify
```

Then **/mcp**, pick projectify and choose Authenticate.

### Claude Code · one command

Just the tools, no skills or hook. Good for a quick try.

```sh
claude mcp add --transport http --scope user projectify https://api.projectify.si/mcp
```

Then **/mcp** → Authenticate, and approve it in the browser.

### claude.ai

1. Open **Settings › Connectors**, choose **Add custom connector**.
2. Name it Projectify, paste `https://api.projectify.si/mcp`, press **Connect** and approve.
3. Add the skill: download it, then upload it in **Settings › Capabilities › Skills**.

Skill download: https://api.projectify.si/v1/public/skills/projectify.zip

### Claude Code on the web

Cloud sessions cannot sign in with /mcp, but they carry the connectors on your Claude account. Add Projectify on claude.ai (above) once and every cloud session has it. Nothing to set up per repo.

### Claude Desktop

Connectors follow your account: add Projectify once on claude.ai and Desktop has it too. Turn it on from the tools menu in a chat. If the tools don't show, quit and reopen Desktop.

## From a script

Make a key in **Agents › API keys** (an owner or admin key), then run the script below. It answers the questions, makes the first project and invites your team.

```sh
API=https://api.projectify.si/v1
AUTH="Authorization: Bearer $PROJECTIFY_KEY"

# Answer the questions and make the first project in one call
curl -s -X POST "$API/onboarding/apply" -H "$AUTH" -H "Content-Type: application/json" -d '{
  "path": "api",
  "timezone": "Europe/London",
  "answers": {
    "working_on": "Ship the Harbour iOS app",
    "kind": "app",
    "team_size": "2_5",
    "first_goal": { "date": "2027-03-14", "text": "TestFlight build ready" }
  }
}'

# More projects
curl -s -X POST "$API/projects" -H "$AUTH" -H "Content-Type: application/json" -d '{"key":"WEB","name":"Harbour website","type":"website"}'

# Invite the team
curl -s -X POST "$API/invites" -H "$AUTH" -H "Content-Type: application/json" -d '{"email":"maya@example.com"}'
```

Start free: https://app.projectify.si/signup. The product page: [Claude Code](https://projectify.si/claude-code.md).
