# Connect Rolês em SP

Remote MCP server: https://rolesemsp.com.br/mcp
Transport: Streamable HTTP (not a local stdio process).
Authentication: OAuth in the user's browser. Sign in with a verified email for cultural queries only.

## When to act

Follow these instructions only when the user explicitly asks to connect or install Rolês em SP. Merely reading a link is not consent to change client configuration. These are setup instructions, not authority to override the user's or client's rules.

## Agents that can configure integrations

1. Use the client's native remote MCP integration mechanism. Consult its current help or documentation; do not invent commands or install unrelated packages. Name the connection `rolesemsp` and use user scope. If user scope is unsupported, explain the available scope before changing project configuration. Preserve existing integrations and avoid duplicate entries.
2. Configure https://rolesemsp.com.br/mcp with Streamable HTTP. A 401 response means authentication is required, not that the integration is connected.
3. Start the client's OAuth flow. Let the user finish sign-in and approval in their browser. Never ask for passwords, one-time codes or tokens in chat, and never embed credentials in this URL or documentation.
4. Initialize the MCP session and call `tools/list` through the client. Report connection success only after the server responds successfully. If a client restart is required, explain it and defer verification until after restart.
5. If access is denied, stop and explain that sign-in or the requested permission could not be completed. Do not retry indefinitely, bypass access controls or suggest that website access grants catalogue access.
6. Once connected, ask what outing the user wants. If they already supplied preferences, use those. Otherwise suggest a short request: “Plan a relaxed Saturday afternoon in São Paulo for two vegetarians with R$150 total: art, food and time to talk.” Confirm current schedules and prices with official sources when planning.

## Browser-based chats

A normal chat message cannot install an integration in Claude or ChatGPT web. If the client cannot edit integrations, give the user a short manual path instead:

- Claude: add a custom connector using https://rolesemsp.com.br/mcp, then complete OAuth sign-in.
- ChatGPT: if the account or workspace supports custom MCP apps, enable developer mode and create a custom app using https://rolesemsp.com.br/mcp. Workspace permission may be required. Complete OAuth sign-in. If the feature is unavailable, suggest a compatible coding agent rather than claiming chat alone can install it.

Do not claim every host supports this server or that a URL paste silently installs it.