# Set up SecondOS in Cursor, Claude Code and Windsurf in 3 minutes

A step-by-step guide to connecting an MCP memory server to your editor, so your AI tools read a structure-aware map of your repo instead of re-scanning it.

SecondOS speaks the Model Context Protocol (MCP), so any MCP-capable editor can read your codebase map through one interface. Here's how to wire it up.

## 1. Map your repo

```
bunx @secondos/cli push .
```

This builds a structure-aware map of your repo and syncs it — symbols, signatures, routes, and a resolved call graph. Your source stays local; only the map + embeddings leave your machine.

## 2. Print the config for your tool

```
bunx @secondos/cli mcp-config
```

This prints ready-to-paste MCP configuration for **Cursor, Claude Code, Claude Desktop, Windsurf and VS Code**. Pick your tool and drop it in:

- **Claude Code:** `claude mcp add secondos -- secondos mcp /path/to/repo`
- **Cursor / Windsurf / VS Code:** add the printed `mcpServers` block to your MCP config (`mcp.json`), then restart.

## 3. Ask it something

Once connected, your tool has 22 SecondOS tools available — `project_overview`, `search_codebase`, `who_uses`, `impact_of`, `schema_drift`, `recall`, and more. Try: *"what does this project do?"* or *"what breaks if I change `verifyToken`?"* It reads the map instead of re-scanning your files.

## Hosted agents (claude.ai, ChatGPT)

For agents that can't spawn a local process, connect over HTTP: mint a project-scoped token in the app and point the agent's custom connector at `https://secondos.app/mcp`. See [Remote MCP](/docs/remote-mcp).

## That's it

No re-explaining, no per-session scan. One map, every tool. Full details in the [MCP docs](/docs/mcp) and the [quickstart](/docs/quickstart).