Connect your AI to the Logic Studio MCP

The steps for connecting an AI tool that supports MCP to your company's Logic Studio, read-only.

1. Before you start

  • You can connect to Logic Studio from an AI tool that supports MCP. If the connection does not work, leave a request on the support board (section 5).
  • The connection is read-only. There are no tools that let the AI change data, and personal-data fields and person-level records (HR, payroll, attendance) are not shared.
  • Responses go to the AI company your company chose. Your company pays that company for the AI service under the contract between your company and that AI provider. Charges for Microsoft products also follow the contract between your company and Microsoft. The Logic Studio MCP add-on fee is billed separately as stated in the connection terms.
  • Only your company's administrators (owner, admin) turn on the connection and register or approve connected services. The connection starts only after an administrator other than the one who registered it enters your internal approval document number and approves it.

2. Prepare in Logic Studio (administrator)

  1. From your name menu at the top right, open "MCP connection" and go to the "Settings" tab. Check each item of the "Connection terms", select "I have read and agree to the connection terms above", then switch on "Turn on MCP connection".
  2. On the "Connection scope" tab, classify the fields to share through MCP on each screen as "Allowed (not personal data)" and press "Save classification". Fields you have not classified and newly added fields are not shared. "Preview 3 rows" shows in advance what would be shared.
  3. The connection address appears under "Endpoint" on the "Settings" tab: https://logicstudio.vexplor.com/mcp

3. Connect a Microsoft Copilot Studio agent

Copilot Studio connects using OAuth 2.0 "Manual". API keys cannot be used (customer companies accept OAuth connections only).

  1. In Copilot Studio — go to the agent, then Tools, Add a tool, New tool, Model Context Protocol, and enter a name, a description and the server URL https://logicstudio.vexplor.com/mcp. Choose OAuth 2.0 for authentication and "Manual" for the type, press Create, then copy the callback URL shown on screen.
  2. Logic Studio administrator — open "MCP connection", the "Connected services" tab, then "Register a connected service". Enter the values below and press "Register".
    • Connected service name: Microsoft Copilot Studio
    • Redirect URLs: the callback URL copied in step 1 — it must match character for character
    • Scopes: choose only what you need ("Questions (ask)", "Screen list · field descriptions", "Screen rows", "Follow relations")
    • Purpose: 10 to 300 characters
    • Client type: "Confidential (client secret + PKCE)"
  3. Another administrator — "Approve" that connected service (enter the "Internal approval document number"). Immediately put the secret shown in the "Client secret — shown only this once" window into Copilot Studio. It cannot be shown again after you close the window; if lost, get a new one with "Rotate secret".
  4. Copilot Studio manual OAuth fields — enter the values below.
    • Client ID: the value in the "Client ID" column of the "Connected services" list
    • Client secret: the value received in step 3
    • Authorization URL: https://logicstudio.vexplor.com/oauth/authorize
    • Token URL and refresh URL: https://logicstudio.vexplor.com/oauth/token
    • Scope: only those chosen in step 2 out of ask screens rows graph (separated by spaces)
  5. Create a new connection and add it to the agent. When the "Approve MCP connection" screen opens on the first question, sign in again with your Logic Studio email, password and "Verification code (6 digits)" (within 5 minutes), review the scopes to be shared, then press "Approve".
  6. Generative orchestration must be on in the Copilot Studio agent settings for the MCP tools to appear. If your company's Power Platform data policy (DLP) blocks the MCP connector, the tools may not appear — check with your company's Microsoft administrator.

Token lifetime: access token 1 hour, refresh 30 days (reissued on every use). If the account is disabled, its role changes, or its password or two-step verification is reset, the connection is cut immediately and you must sign in and approve again.

4. Microsoft 365 Copilot (declarative agent) — for developers

To use it from Microsoft 365 Copilot, your company's developer must build and upload a declarative agent app with an MCP plugin using the Microsoft 365 Agents Toolkit. This path connects with an OAuth authorization code (static registration); API keys cannot be used.

  • Registration on the Logic Studio side is the same as steps 2 and 3 of section 3. For the redirect URL, enter https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect.
  • Enter the client ID, secret, authorization URL and token URL (section 3, step 4) in the app's OAuth settings.
  • Your company's Microsoft 365 administrator must have custom app upload and Copilot access turned on.
  • For the Agents Toolkit version requirements and detailed steps, follow the official Microsoft documentation ("Build a plugin for a declarative agent from an MCP server").

5. If it does not connect — leave a request on the support board

Leave it from "Support" at the top, then "New request". WACE checks it and replies. Only requests left by people in your company are visible.

  • Type: "External AI connection"
  • Please include: the error message exactly as shown on screen, the AI tool you use (for example Copilot Studio), and the time it happened
  • Do not enter passwords, tokens or client secrets. A request containing anything that looks like such a value is not saved.
  • If the error message contains a long value, remove it before sending. Long values may not be saved even if they are not secrets.

Common messages, which the server shows in Korean: 「PKCE(code_challenge_method=S256)가 필요합니다」 (PKCE is required), 「이 회사는 OAuth 연결만 받습니다」 (this company accepts OAuth connections only), 「되돌아갈 주소가 이 연결 서비스에 등록한 주소와 다릅니다」 (the redirect URL differs from the one registered for this connected service), 「지원하지 않는 프로토콜 버전입니다」 (protocol version not accepted). Quoting the message as it appears helps us find the cause quickly.

More

Checked against the code on