← Toutes les connexions

Connexion avec Microsoft Copilot Studio

Copilot Studio — NewAlgorithm as an MCP tool for your corporate agent.

Avant de commencer, créez votre compte gratuit.Créer un compte

Ce contenu est disponible en anglais.

Quel MCP allez-vous connecter ? Les commandes ci-dessous s'adaptent à votre choix.

  1. 1

    Generate your API key

    Sign in to app.newalgorithm.io with your account, open Keys & apps and generate a key. It is shown only once: copy it and store it somewhere safe.

    Key format
    na_live_xxxxxxxxxxxxxxxxx
  2. 2

    Open the agent's tools

    In Copilot Studio, open the agent and go to Tools → Add a tool → New tool → Model Context Protocol.

  3. 3

    Enter the server

    Fill in the name, the description and the server URL. For authentication, choose the option for an API key sent in the Authorization header.

    Server URL and header
    https://totvs.mcp.newalgorithm.io/mcp
    Authorization: Bearer na_live_xxxxxxxxxxxxxxxxx
  4. 4

    Or publish it as a custom connector

    If you need Power Platform governance, you can declare NewAlgorithm as a custom connector. What marks the connector as MCP is the x-ms-agentic-protocol extension:

    Connector OpenAPI definition
    swagger: '2.0'
    info:
      title: NewAlgorithm
      description: Specialized knowledge of SAP and enterprise architecture
      version: '1.0'
    host: mcp.newalgorithm.io
    basePath: /
    schemes:
      - https
    paths:
      /mcp:
        post:
          summary: MCP Server
          operationId: InvokeMCP
          x-ms-agentic-protocol: mcp-streamable-1.0
          responses:
            '200':
              description: Success
  5. 5

    Create the connection with the key

    When you add the tool to the agent, Copilot Studio asks for a connection. That's where the API key is stored — inside the Power Platform environment, not in the agent.

  6. 6

    Test and publish

    In the test panel, ask an SAP question. The na_* tools show up in the activity trace when the agent uses them. Publish once you've confirmed it works.

    Résultat attendu : na_prepare, na_search, na_route, na_specialists, na_version

The connection lives per Power Platform environment: configure it in each environment (dev, test, production) and apply your organization's DLP policies to the connector.

Détails sur l'authentification et les outils dans la Documentation.