> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rings.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Microsoft Copilot Studio

> Add Rings as an MCP tool on a Microsoft Copilot Studio agent

<Steps>
  <Step title="Open your agent's tools">
    In Copilot Studio, open the agent, go to the **Tools** page, and select
    **Add a tool**.
  </Step>

  <Step title="Choose Model Context Protocol">
    Select **New tool**, then **Model Context Protocol**. The MCP onboarding
    wizard opens.
  </Step>

  <Step title="Fill in the server details">
    | Field              | Value                                                                            |
    | ------------------ | -------------------------------------------------------------------------------- |
    | Server name        | `Rings`                                                                          |
    | Server description | Relationship intelligence — people, companies, communications, and deal activity |
    | Server URL         | `https://production-api.joinrings.com/mcp`                                       |
    | Authentication     | **OAuth 2.0**                                                                    |

    The orchestrator uses the server description to decide when to call Rings at
    runtime, so keep it specific.
  </Step>

  <Step title="Create the connector">
    Finish the wizard. Copilot Studio creates a custom connector in your
    environment for the Rings MCP server.
  </Step>

  <Step title="Add it to the agent">
    Back on **Tools → Add a tool → Model Context Protocol**, pick **Rings** from
    the list, authorize the connection, then select **Add to agent** (or **Add
    and configure** to review the tools first).
  </Step>

  <Step title="Test it">
    Use the test pane and ask something that needs the graph, for example
    "Who at our firm has the strongest relationship with Acme Corp?"
  </Step>
</Steps>

<Note>
  Copilot Studio connectors live in a Power Platform environment. If the agent
  will be shared, make sure the connector is created in the environment the
  agent is published to, and that users have permission to the connection.
</Note>

## API key alternative

If you prefer a service identity over per-user OAuth, choose **API key** as the
authentication type and configure the header name as `x-api-key`. Every request
then runs with that key's tenant scope rather than the signed-in user's — add
`x-rings-user-id` if the agent needs per-user context for meetings, tasks, or
writes.