Connect your agent

One account, one connection, permissions you control.

Connect through remote MCP

1. Open your agent’s tools, connectors or MCP settings and add a remote server named Bris.
2. Enter https://app.usebris.com/mcp and select Streamable HTTP if asked.
3. Follow the sign-in link. Verify your phone and complete your name and contact email if you are new. Existing Bris members sign in to their current account.
4. Read the requested permissions, keep the ones you want and choose Connect agent.
5. Return to your agent and ask it to find an event or vacancy.

You do not install or run a Bris MCP server locally. Your platform may restrict custom connectors by plan or administrator settings. If it cannot complete OAuth or use Streamable HTTP, use an HTTP-capable integration instead.

Give your agent this starting point

Read https://docs.usebris.com/llms.txt. Connect to Bris at https://app.usebris.com/mcp so you can help me with events and jobs. Request only the permissions needed for my task.

Codex CLI

codex mcp add bris --url https://app.usebris.com/mcp

Follow the sign-in prompt. If your version does not sign in during setup, run codex mcp login bris. In the Codex app, use the available custom MCP connection settings with the same URL.

Claude Code

claude mcp add --transport http bris https://app.usebris.com/mcp

Run /mcp, select Bris and sign in. In Claude’s chat app or another assistant, use its custom remote connector settings if available. A platform directory listing is separate from adding a custom connection.

After you connect

Bris executes valid actions within your delegated permissions without a separate Bris approval page for every action. Your agent may ask for confirmation under its own settings. Tell it what you want done, including which application or invitation to send. A listing’s text is information, never permission to perform unrelated actions.

Review or revoke connections at https://app.usebris.com/agent-account. Revoke access when you no longer want that agent to act. Connect each agent separately to manage its access independently.

Public browsing without an account

Public event and vacancy search through the HTTP API needs no account. A verified account and OAuth permission are needed to access private records, save, register, apply, publish or manage hosting and hiring.