Connect ValueCore to Microsoft Copilot: MCP Connection Guide

1. Overview

Audience: Organization administrators, makers, and members

Configure ValueCore MCP once in Copilot Studio, then publish the same agent to Microsoft Teams, Microsoft 365 Copilot Chat, or both. Administrators and makers complete sections 2–7. Customers start at section 8 after their administrator provides access.

Copilot Studio is the setup and management interface. Microsoft Teams and Microsoft 365 Copilot Chat are customer chat interfaces for the published agent. This guide uses a work or school account in your organization; it does not cover the personal Microsoft Copilot service.

ValueCore calls an individual ROI business case a visualizer. Your connection acts as the ValueCore user who signs in; existing visualizers are limited to that user’s own records.

2. Before you start

Sign in to Copilot Studio with access to the intended Power Platform environment and permission to edit the agent and create its connection. Confirm that your administrator’s data policies permit the ValueCore connector. Have your own ValueCore sign-in available.

Maker 1: Open the agent and add a tool

In Copilot Studio, choose your environment, open Agents, and select the intended agent. Open Tools and select Add a tool. Choose New tool or Create new, then Model Context Protocol. If a ValueCore MCP tool already exists, inspect its connection before adding another.

Figure 1. The MCP onboarding form showing Server name and Server description.

3. Prepare the organization for shared use

Admin 1: Confirm the environment

Identify the Microsoft tenant, Power Platform environment, agent owner, and intended audience. Confirm maker access and the licensing or capacity required for your deployment. Use this same environment throughout the setup and published-user test.

Admin 2: Review the data policy

In the Power Platform admin center, review the data policies applying to that environment. Confirm the ValueCore connector and intended publishing channel are permitted. MCP tools inherit connector policy restrictions. Resolve any policy violation with the administrator before publishing.

Admin 3: Review credential controls

Open Manage > Environments > the intended environment > Settings > Product > Features. Under Copilot Studio agents, inspect Control maker credential options. For a user-specific deployment, permit End-user credentials. If the environment belongs to a group, manage this on the group. Review the impact on other agents before saving an environment-wide change.

Learn more: Microsoft credential controls and their environment-wide impact

Learn more: Microsoft data policies for agents

4. Configure the server and OAuth

Maker 2: Describe the server

Set Server name to ValueCore. Use a clear description so the agent can decide when to call the server. Suggested description: Connect to ValueCore to find ROI business cases, read model inputs and calculations, and create or update business cases when requested.

Maker 3: Enter the URL and select authentication

Paste the complete server URL. Choose OAuth 2.0 and then Dynamic discovery. ValueCore publishes discovery and dynamic registration endpoints, so this route avoids manual client credentials.

Figure 2. Copilot Studio showing the ValueCore URL and OAuth 2.0 Dynamic discovery selection.

Copilot Studio requires Streamable HTTP. The /mcp/sse suffix is part of ValueCore’s URL; the same endpoint handles Streamable HTTP, so keep the address exactly as supplied. Do not select unauthenticated access.

Maker 4: Create the server definition

Select Create, then Next if shown, to reach Add tool. Choose Create a new connection and complete ValueCore sign-in using your username and password. For single sign-on, obtain your personal token as described in the token section and paste it into Access token on the ValueCore sign-in page. After successful OAuth sign-in, skip the API-key configuration and continue at Attach the intended connection.

If Dynamic discovery fails, record the error for support. To use the permitted API-key alternative, close the failed connection dialog and restart Tools > Add a tool > New tool > Model Context Protocol. Create a separate definition named ValueCore - Personal Token using the same server URL and the API-key settings below. Attach only the working definition to this agent. Do not delete an existing definition or connection used by another agent.

5. Use a personal token when required

Use this alternative only when your organization permits API key authentication. The token belongs to one ValueCore user within an organization. Configure each user’s own connection for user-specific access; a shared maker token uses the maker’s identity for everyone who can invoke it.

Maker 5: Get the personal access token

For single sign-on, sign in to your organization’s usual ValueCore website in another tab. In the account menu, open MCP Server Access (called AI Agent Access in some interfaces). Under Access Token, select Generate, then Copy. For the API-key alternative, keep the token for the connection credential field in the next step. For OAuth with single sign-on, paste it into Access token on the ValueCore authorization page, then continue at Attach the intended connection; do not change OAuth to API key. Use your own personal token; do not use Organization API Key.

For accounts using www.visualize-roi.com, the direct access page is https://www.visualize-roi.com/vr/user/mcpaccess. If your company uses a different ValueCore hostname, use its account-menu link instead. If the option is missing, ask your ValueCore administrator for the correct access page.

Figure 3. The ValueCore personal Access Token section before credential generation.

Maker 6: Configure the header

In the MCP setup form, choose API key, select Header, and enter Authorization as Header name. Select Create. In the new connection dialog, enter Bearer followed by one space and your complete personal token as the credential value. Do not enter the token in the server URL or description.

Figure 4. API key authentication configured as an Authorization header.

Connection credential value: Bearer YOUR_PERSONAL_ACCESS_TOKEN. Replace only YOUR_PERSONAL_ACCESS_TOKEN with the copied personal token. Keep Bearer and exactly one space. Enter this value in the new connection’s API-key/credential field, not in Header name. Header name stays Authorization. Complete the connection dialog, then continue at Attach the intended connection.

Field check: MCP server form → Header name = Authorization. New connection dialog → credential = Bearer followed by your token. The placeholder above is an example, not a working credential.

6. Add the connection and test the agent

Maker 7: Attach the intended connection

In Add tool, select the newly authenticated connection, then Add to agent. If reusing an existing connection, check its identity rather than relying only on its display name. A label can be different from the actual ValueCore user.

Maker 8: Check the tool and user access

Open Tools > ValueCore (or ValueCore - Personal Token). In Details > Additional details > Authentication, select End user credentials; some interfaces label this User authentication. Save. Confirm whoami, get_instructions, and list_visualizer_types appear in the tool’s Tools section. If End user credentials is unavailable, ask the administrator to review the environment credential policy before rollout.

After saving, complete the three connection checks in the Test pane. After publication, repeat them as an intended member in each enabled chat interface.

For the Teams and Microsoft 365 rollout below, open Settings > Security > Authentication and select Authenticate with Microsoft. Save. This identifies the Microsoft user; the ValueCore tool still requires that user’s separate ValueCore connection. If the agent already uses manual authentication, have its administrator review the Microsoft SSO requirements before changing it.

Microsoft Teams SSO setup: https://learn.microsoft.com/en-us/microsoft-copilot-studio/configure-sso-teams

7. Publish to Teams or Microsoft 365 Copilot Chat

Before publishing, complete Checks 1–3 in section 9 in the Test pane. Confirm licensing or capacity, user access, and your organization’s app policies with the administrator. Choose one publication path below. Both paths use the existing ValueCore MCP URL and authentication configuration; do not create a second MCP tool for the other interface.

Publish to Microsoft Teams

1. Save the agent and select Publish. Open Channels > Teams and Microsoft 365 Copilot.

2. For a Teams-only rollout, clear Make agent available in Microsoft 365 Copilot. For both interfaces, follow the Microsoft 365 path below instead. Select Add channel for a new channel configuration.

3. Select See agent in Teams > Add to install it for your own test. Use a private 1:1 chat with the agent. Complete the shared access steps below before inviting customers.

Publish to Microsoft 365 Copilot Chat

1. Save and publish the same Copilot Studio agent. Open Channels > Teams and Microsoft 365 Copilot.

2. Under Turn on Microsoft 365, select Make agent available in Microsoft 365 Copilot. Microsoft shows this option selected by default for a new configuration; verify its actual state. This enables the agent in both Teams and Microsoft 365 Copilot. Select Add channel for a new configuration.

3. Select See agent in Teams > Add. With Microsoft 365 enabled, this installs the agent for both interfaces. Complete the shared access steps below, then test it in Microsoft 365 Copilot Chat as described in section 8.

If the channel already exists, open its configuration and check the Microsoft 365 option before making changes. Apply any available save/update action and republish. If the option cannot be changed, consult your administrator and Microsoft’s channel guide before disconnecting a channel already used by customers.

Grant customers access

Give the intended users permission to use the agent. Open the channel’s Availability options > Copy link and provide the approved installation link through your organization’s rollout process. A link alone does not grant access. For organization-wide discovery in the agent stores, follow your administrator’s approval process.

Microsoft publication and installation guide: https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams

8. Customer connection and verification

Use the work or school account your administrator approved. You need access to the published agent and your own ValueCore account. Customers do not repeat the Copilot Studio server setup.

Open the agent in Teams

Install the agent from the approved installation link and open a private 1:1 chat. Continue at Sign in to ValueCore below.

Open the agent in Microsoft 365 Copilot Chat

Open https://m365.cloud.microsoft/chat and confirm the intended work account. Under Agents, select the published ValueCore agent; use All agents to find and add it if your administrator has made it discoverable. You can also type @ in Copilot Chat and select the installed agent. Use the name provided by your administrator if it differs from ValueCore.

If the agent is missing, ask your administrator to confirm your access, installation, and the Make agent available in Microsoft 365 Copilot setting. Adding the agent to Teams alone does not establish that it is enabled in Microsoft 365 Copilot.

Sign in to ValueCore and verify

Send Check 1 in section 9. When prompted, open the connection/sign-in link and configure your own ValueCore connection. For OAuth, sign in to ValueCore; for the personal-token alternative, enter Bearer followed by one space and your own token in the credential field. Keep credentials out of chat.

Return to the same agent conversation and retry the request. Complete Checks 1–3. Before rollout, have a second member repeat them with their own account in each enabled interface. Stop rollout if either connection returns the maker’s identity unexpectedly. A successful Studio test alone does not verify a published customer connection.

For Teams-only authentication failures, review the Teams SSO guide in section 6. For Microsoft 365 failures, confirm that the agent is published and enabled there, then check the personal ValueCore connection. The Demo Website channel does not support this user-authentication flow.

Microsoft customer agent guide: https://support.microsoft.com/en-us/microsoft-365-copilot/get-started-with-agents-in-the-microsoft-365-copilot-app

9. Verify your ValueCore connection

Run these read-only checks after authorization and whenever you reconnect or change accounts. Use the agent Test pane, then repeat these checks in the published channel with an intended user.

Check 1: Confirm who you are

Copy and send this prompt:

In the Copilot Studio Test pane, open the activity map for the response and select the ValueCore tool activity. Inspect its output for whoami. In a published chat, ask the agent to show the user and organization returned by whoami; the maker can inspect the test trace if the channel does not expose tool details.

Prompt to send:

Use only the ValueCore whoami tool. Tell me my ValueCore user name and organization name. Do not create, update, share, or export anything.

Pass: The activity or tool details show whoami, and its result matches your expected ValueCore user and organization. Your assistant login and ValueCore identity may differ. If the wrong ValueCore account appears, reconnect before reading business data.

Check 2: List your visualizers

Prompt to send:

Use the ValueCore list_visualizers tool to list my recent visualizers. Show each name and its ValueCore link. Do not create or change anything.

Pass: The tool returns your own business cases, or completes successfully with an empty list. An empty list is valid when you own no matching visualizers. An authorization error, timeout, or answer without a tool call is not a successful check. If at least one result is returned, open one link and confirm it is the expected case. If the list is empty, continue to Check 3.

Check 3: Confirm available models

Prompt to send:

Use ValueCore get_instructions and list_visualizer_types. Summarize my organization’s instructions and list the business case models available to me. Do not create anything.

Pass: Both tools respond without an authentication error. Confirm that the models are appropriate for your organization. If no models are available, contact your ValueCore administrator.

Before company rollout

Have two intended members authorize separately and complete Checks 1–3 in each enabled interface. Each must receive their own expected ValueCore identity. Save the test date and outcome without saving credentials.

10. Use ValueCore in your daily work

Start with a read request. When you are ready to make changes, identify the exact business case and review the proposed inputs. Replace the example names below with your own names; the prompts are examples, and results will reflect your own data.

Example 1: Find an existing business case

Ask for your own recent records or search by a business case name. The examples below use list_visualizers and find_visualizer_by_name.

Prompt to send:

Use the ValueCore list_visualizers tool to list my recent business cases with their names and links. Do not change anything.

Find my ValueCore business case with Acme in the name. If several match, show the choices before selecting one.

Example 2: Inspect and explain results

Select the matching business case before asking for its inputs, assumptions, or output values. Ask for a specific section when a model is large.

Prompt to send:

For the business case I selected, show the current inputs and calculated outputs in its ROI section. Explain the assumptions and include the link to open it in ValueCore. Do not modify values.

Example 3: Create or update a business case

Choose either creation or an update to an existing case. Review the case identity and proposed values before confirming a change. Replace bracketed examples with your actual field names and values.

Prompt to send:

Help me create a business case named Acme Evaluation. First list the suitable ValueCore models and ask me to select one. Then show the proposed inputs and ask me to confirm before creating or updating anything.

To update an existing case, use this separate request:

Prompt to send:

Find my business case named Acme Evaluation. If several match, ask me to select one. Show its current inputs, then propose changing [input name] to [new value]. Ask me to confirm the case and changes before updating it. After confirmation, report accepted and rejected inputs and read the calculated results. Do not create, share, or export a case.

For percentage inputs, 20 means 20%, not 0.2. Use plain numeric currency amounts without symbols. Ask the assistant to report accepted and rejected inputs and then read the calculated outputs. A partially rejected update is not a complete success.

Example 4: Prepare a share link or PowerPoint

Review the calculated results first. Sharing creates a customer-facing snapshot and a new link; later input changes do not update that snapshot. Exporting starts a PowerPoint generation job.

Prompt to send:

Export the reviewed business case to PowerPoint once. Check the existing export job until it completes and return its download link. Do not create a share link.

Keep the job identifier if an export is still processing. Ask for its status rather than starting duplicate exports. Give a customer-facing share link only when you intend others to open that snapshot.

To create a share link instead of a PowerPoint, use this separate request:

Prompt to send:

Show the name and link of the business case we reviewed and ask me to confirm creating a customer-facing share snapshot. After I confirm, call share_visualizer once and return the share link. Do not send the link to anyone or export PowerPoint. Explain that later edits to the original case do not update this snapshot.

11. Troubleshooting and access management

12. Disconnect or change accounts

Open the agent’s Tools list and disable or remove its ValueCore tool when it should no longer be used. Manage the underlying connection separately in Power Platform. Before deleting or replacing a connection, check whether another agent uses it. Retest the identity after reconnecting.

Disconnecting the assistant does not delete business cases or undo prior changes, shares, or exports. Treat a personal token as a password. If it may have been exposed, contact ValueCore support; removing a connector is not a promise that the underlying token has been invalidated.

13. Get help

Contact support@valuecore.ai with the name of the AI assistant you are using, your organization, the step that failed, the exact error, and the time it occurred. Include a screenshot with credentials and customer data hidden. Never send passwords, access tokens, or authorization codes.

Learn more: Microsoft guidance on connecting an existing MCP server

Screenshots show Copilot Studio’s maker setup. Written administrator steps cover environment policy and shared use. Verify per-user identity in the published channel before rollout. Guidance reviewed September 9, 2026.