Model Context Protocol (MCP) connects an AI application to Halo. This guide calls that application the client.

Halo hosts the MCP server. You do not need to install a server. The connection has two read-only tools: search_halo and get_halo_details. These tools cannot send messages, publish requests, or change Halo records.

How do I set up team-wide access to the MCP?

Preamble: Prepare AI client access

• If you don’t already have one, select a centrally managed client that supports remote MCP, Streamable HTTP, browser-based OAuth authorization, and publishing a connection to users across your workspace.

  • Examples of AI applications include Copilot, Claude Cowork, and Glean. Confirm that your chosen client's plan and administrator settings support centralized setup with per-user authentication.

• Get IT approval for the client, its AI provider, and its storage of tokens, prompts, and results.

Prepare Halo MCP access

• Ask your Halo account contact to confirm MCP access for your company.

• Select a test user with a verified Halo sponsor account in that company.

• Confirm that the test user can sign in at Halo.

Each user must connect with their own Halo account. Do not share accounts or tokens. If your company uses single sign-on (SSO), confirm the existing Halo sign-in process with your Halo contact. This guide does not cover SSO setup.

IT: configure and publish the connection once

1. Open the client's administrator-level MCP or connector settings. Menu names depend on the client.

2. Add a remote MCP server with the name Halo.

3. Enter this server URL: https://www.halo.science/mcp.

4. If the client asks for a transport, select Streamable HTTP.

5. Select OAuth authorization with each user authenticating through their own account. Let the client read Halo's connection metadata.

6. Publish or enable the connection for all users in your company's workspace using the client's access settings. The Halo connection then becomes discoverable in their accounts.

7. Add the Halo skill, available from your account contact, to your client and enable for all employees to support better MCP discoverability and operation.

Centralized setup makes the connection available; it does not sign users in to Halo or grant them a Halo account. The steps below apply across supported clients rather than prescribing client-specific menus.

Users: authenticate at time of use

1. Find and select the Halo connection in your AI application.

2. When prompted to connect or authorize at time of use, sign in directly to Halo in the browser with your own Halo account.

3. Complete the authorization steps and return to the AI application.

Each user's authorization is separate.

Test the connection

Use the test user's account to confirm that Halo is discoverable after IT publishes the connection.

Follow the user authentication steps above, then:

1. Ask the client: “Use Halo to find biodegradable packaging solutions.”

   1. Check that the client calls search_halo

2. If a result is available, ask: “Show me more details on the first Halo result.”

   1. Check that the client calls get_halo_details

3. Open a returned Halo link.

Correct connection problems