For agents and technical readers

Connect a coding client and verify identity

Use the Mind’s trusted connection guide and the person’s OAuth sign-in, then verify the actual Mind tools.

Contents

Trusted address and authority

Ask the person to open the intended Mind’s Portal, Apps & Tools, then Connect a tool as you. Use the loaded MCP URL and the selected client’s instructions. Do not infer an endpoint, copy another person’s token or treat an OAuth sign-in as proof that the intended identity reached the Mind.

Claude Code

The released Portal guide supplies this command shape. Substitute the trusted URL supplied by that Mind.

claude mcp add --transport http mind <MCP_URL_FROM_PORTAL>

Complete browser sign-in as the intended person. Follow the Portal’s standing-rule step for personal or project instructions. A changed account needs the named Mind server removed and added through the supported flow.

Codex

The released Portal guide supplies these command shapes:

codex mcp add mind --url <MCP_URL_FROM_PORTAL>
codex mcp login mind

Complete browser sign-in as the intended person. Add required = true under [mcp_servers.mind] in ~/.codex/config.toml as the current Portal guide instructs, so startup waits for the Mind tools. Remove only a pre-existing static bearer override for this Mind entry if the guide identifies one. Leave unrelated servers/configuration alone. Use the current displayed guide if the installed client differs.

Verify and test one read

Start a fresh client conversation, discover the advertised tools and call orient {}. Check the Mind, user identity and scopes. A legacy me principal is not the expected named OAuth person; reconnect the named server rather than creating another personal token. Follow the relevant map and read a harmless authorised record.

Failure and completion

For stale authorisation, wrong identity or missing membership, follow the named client’s reconnect route and have the owner inspect intended membership/grants. Retry transient read contention briefly; do not bypass a denied action. Finish with the verified principal and read result, or a precise sign-in/client/authority blocker. Configuration alone is not an acceptance pass.

Related

Portal, MCP and CLI · Ask your first question

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://app.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Connect a coding client and verify identity

Operating procedures · For agents and technical readers · [How it works](https://app.mensara.ai/how-it-works)

Use the Mind’s trusted connection guide and the person’s OAuth sign-in, then verify the actual Mind tools.

[Page as Markdown](https://app.mensara.ai/how-it-works/connect-client-procedure.md)

[Human guide](https://app.mensara.ai/how-it-works/portal-mcp-cli)

## Connect a coding client

Availability: Use the current workspace setup instructions.

Limits: Codex CLI and Claude Code first-use journeys require separate qualification.

## Trusted address and authority

Ask the person to open the intended Mind’s Portal, **Apps & Tools**, then **Connect a tool as you**. Use the loaded MCP URL and the selected client’s instructions. Do not infer an endpoint, copy another person’s token or treat an OAuth sign-in as proof that the intended identity reached the Mind.

## Claude Code

The released Portal guide supplies this command shape. Substitute the trusted URL supplied by that Mind.

```
claude mcp add --transport http mind <MCP_URL_FROM_PORTAL>
```

Complete browser sign-in as the intended person. Follow the Portal’s standing-rule step for personal or project instructions. A changed account needs the named Mind server removed and added through the supported flow.

## Codex

The released Portal guide supplies these command shapes:

```
codex mcp add mind --url <MCP_URL_FROM_PORTAL>
codex mcp login mind
```

Complete browser sign-in as the intended person. Add `required = true` under `[mcp_servers.mind]` in `~/.codex/config.toml` as the current Portal guide instructs, so startup waits for the Mind tools. Remove only a pre-existing static bearer override for this Mind entry if the guide identifies one. Leave unrelated servers/configuration alone. Use the current displayed guide if the installed client differs.

## Verify and test one read

Start a fresh client conversation, discover the advertised tools and call `orient` `{}`. Check the Mind, user identity and scopes. A legacy `me` principal is not the expected named OAuth person; reconnect the named server rather than creating another personal token. Follow the relevant map and read a harmless authorised record.

## Failure and completion

For stale authorisation, wrong identity or missing membership, follow the named client’s reconnect route and have the owner inspect intended membership/grants. Retry transient read contention briefly; do not bypass a denied action. Finish with the verified principal and read result, or a precise sign-in/client/authority blocker. Configuration alone is not an acceptance pass.

## Related

- [Portal, MCP and CLI](https://app.mensara.ai/how-it-works/portal-mcp-cli)
- [Ask your first question](https://app.mensara.ai/how-it-works/first-useful-question)

[Join the waitlist](https://app.mensara.ai/#waitlist)