Brain ScannerConnect a coding agent and map your first project
Open your dashboard. Sign in or create an account and confirm your email when asked. A new account opens an empty project. Rename it to match the project you want to work on.
Connect your agent from the dashboard
Select Connect agent beside Agent not connected. Use the instructions for your client. The hosted endpoint is:
https://brainscanner.dev/mcp/v2Brain Scanner uses Streamable HTTP MCP with browser authorization. Your agent needs support for that connection type. Website sign-in alone does not connect an agent.
For Codex CLI, add the connector and complete its browser login:
codex mcp add brain-scanner --url https://brainscanner.dev/mcp/v2
codex mcp login brain-scannerFor Claude Code, add the remote connector, then use /mcp in Claude Code to authenticate:
claude mcp add --transport http brain-scanner https://brainscanner.dev/mcp/v2In clients that offer a custom remote MCP connection, enter the endpoint in their connector settings and follow their authorization flow. Client support and account availability vary; the dashboard has the same setup instructions.
Review the permissions yourself. The connector's fixed profile includes project metadata reads, writes, export and deletion. Access to your local files, repository and terminal remains controlled by your agent's own permissions. Do not paste passwords or authorization callback links into a chat.
Start with one useful question
Choose one area you want to understand: where a task is created, which callers use a shared helper, or which tests cover a change. The session recovery example shows how recorded changes and checks help you choose a focused next step.
Give the agent one specific project
Ask the agent to use list_linked_projects and choose the project by its name and ID. Use the same account in the browser and the agent. For a new account, select the empty project already opened in your dashboard.
Tell the agent which local project it may inspect and what question you want the map to answer. For example:
Use Brain Scanner for my selected project [name and ID]. Inspect the local project [path I choose] using your existing permissions. Map its main parts and relationships so I can understand where a requested change belongs. Publish privacy-filtered project metadata to that project. Exclude source contents, credentials and secrets. Keep source files unchanged. Ask if access or scope is unclear or a new charge needs approval. Return the dashboard link and identify one useful area to inspect.
Send this as a task in your connected coding agent. Brain Scanner's website does not start a local scan. The project stays empty until the agent publishes a map.
Check the result
Open Project Graph to inspect the published nodes and relationships. Select an area to see its recorded details. Treat missing paths or old information as questions for the agent to check against the current project.
If Agent not connected remains visible, ask the agent to list your projects, then choose Check connection in the dashboard dialog. If authorization succeeded but tools are missing, open a fresh agent conversation. If a different project appears, check the signed-in account and selected project ID before publishing anything.
For an authorization error, retry the client's normal login. For a mapping error, ask the agent what failed and what was actually saved. Contact support with the error and client name, without credentials or private project content.
Review the work and continue
Use the agent-change review guide to compare the recorded result with your request.
Follow the codebase impact analysis example to trace a change through callers and tests. When you return later, use the resume a coding project guide to check recorded context and choose the next task.