WorkPoint 365 MCP Setup – Welcome! How can we help?

1. Introduction

The WorkPoint 365 MCP (Model Context Protocol) enables AI agents to securely access and interact with data from your WorkPoint 365 solution using the permissions of the signed-in user. The initial release focuses on read-only access, allowing agents to retrieve, search, and summarize information while respecting existing user permissions and security boundaries.

In this article, we will walk through how to configure and manage the WorkPoint 365 MCP in WorkPoint 365 Administration. You will learn where to enable the MCP, how to configure its settings, and how to prepare the MCP for use with WorkPoint agents and custom AI agents.

If you are new to the WorkPoint 365 MCP and would like an overview of its purpose, architecture, and capabilities before proceeding, we recommend reading this article.

Once the MCP has been configured, it can be connected to agents such as the standard WorkPoint Agent, Microsoft Copilot agents, or custom agents built by partners and customers, enabling them to securely work with information stored in your WorkPoint solution.

2. WorkPoint 365 MCP Setup

The WorkPoint 365 MCP can be set up and managed inside the WorkPoint 365 administration:

In the WorkPoint 365 administration, expand the "Features" section and click "MCP".

This opens the MCP setup page:

3. Initial capabilities setup

By default, no capabilities are set up for new solutions, but clicking the "Regenerate default configuration" button in the top panel scaffolds the MCP capabilities according to the current business module hierarchy, as well as master site list setups.

Click the "Regenerate default configuration" button to scaffold the WorkPoint 365 MCP capabilities according to the current solution-, business module- and master site setups.

The WorkPoint solution used for demonstration here contains two business modules; Customers and Projects.

If we click the "Regenerate default configuration" button, a confirmation dialogue is displayed, asking you to acknowledge that your current configuration will be overwritten, and that this cannot be undone:

Clicking the "Regenerate" button will scaffold the MCP capabilities according to the business module- and master site list setups on the solution (the scaffolding operation may take a few seconds):

MCP capabilities are grouped inside sections for the solution root and one section per business module.
Inside each group, capabilities are automatically generated for various actions the MCP can help AI agents perform. Examples could be to create new entities within the Customers business module, or to get document items from the Documents library on a Project site.

4. Editing MCP capability properties

Each WorkPoint 365 MCP capability has several properties which can be tweaked. These properties can be found in the right-side "Capability properties" panel when a capability is selected.

Capability property	Purpose	Notes
General
Display name	This property contains a human readable name for the capability. It is not used by the MCP server operations, only to make capabilities more identifiable for users.
Description	This property contains instructional guidance for the agent about when and how to use this capability/tool action. You can elaborate on the default text provided, or provide your very own set of instructions to make the use and purpose of the capability more understandable to agents using the WorkPoint MCP. If your agent has trouble using this capability in situations where it should be applied, you can try providing better instructions in this field.
Enabled	If disabled, agents using the WorkPoint MCP will treat this capability as unavailable and will not attempt to use it.
Create site	Use this option to set whether the operation executed using this capability should create an entity site.	This option is available on capabilities using the "CreateEntity" operation only.
Add alias	Use this field to provide synonyms and/or phrases agents using the WorkPoint MCP can attempt to match in prompts to map requests to this capability.
Field Policy
Allowed Write Fields	The contents of this list varies depending on which type of capability is selected. CreateEntity/UpdateEntity: The list contains fields that the capability is allowed to write when creating data in the WorkPoint solution, for example when creating or updating new entities. These fields come from the business module list. SearchEntities/SearchDocuments/SearchItems: The list contains fields that the agent should display in search results using this capability. These are pulled from mapped managed properties from the SharePoint Search Schema, mapped to site columns on the business module. If your custom column does not appear here, ensure that it is a site column on the root site, and that it is mapped to a managed property in the SharePoint Search Schema. After the property h as been crawled, it should appear in this list.
Limits
Maximum Results Per Page	Use this field to set a hard limit for the number of results the agent/tool call can return in one result page. Default = 100.
Maximum Search Query Length	Use this field to set a maximum query payload the agent can send to this capability. Default = 500.
Advanced
Raw Capability JSON (Agent Tool Contract)	Use this field to edit the capability in raw JSON format.	Editing and applying JSON is temporarily disabled in this view.
Capability Schema Preview (Auto-generated Tool Contract)	Use this field to inspect the capability schema.	Editing and applying JSON is temporarily disabled in this view.

Individual capabilities can always be reset back to their default values provided by WorkPoint. To do this, follow these steps:

Several capability properties have been customized.
To reset the capability properties back to default values, we click the "Reset Capability" button.

In the configuration dialogue, we click "Reset Capability".

After a couple of seconds, the properties are set back to default values.

You may have to switch away and back to the capability to see the default values after performing a reset.

5. Adding the WorkPoint 365 MCP to an agent

Custom Microsoft Copilot Agents

To use the WorkPoint 365 MCP in custom Microsoft Copilot agents, you can add it as a tool for the agent.

You can create a custom Microsoft Copilot agent in Microsoft Copilot Studio:

In Copilot Studio, open the "Agents" page.
On the Agents page, click the "New agent" multi-button and select "Agent (Standard)".

Give the agent a name fitting for it's purpose. You can also review the additional Agent settings. In this case, we do not change any of them.

The agent is now being created. Once finished, it should look something like the following:

We can now begin by providing the agent with a set of instructions. In this instance, we provide it information about how to behave when assisting in Project Management related tasks and questions:

In the "Instructions" section, click the "Edit" button.

Type or paste your instructions into the editor and when satisfied, click the "Save" button.

Next, we will add the WorkPoint 365 MCP to the agent:

Scroll down to the "Tools" section and click "Add tool".

Search for "workpoint".
In the "Model Context Protocol" section, select "WorkPoint 365 MCP".

Click the Connection options and create a connection using an admin- or service account.

When asked, provide consents for the required permissions.

When the connection has been created, click the "Add" button.

This adds the WorkPoint 365 MCP to the Copilot agent:

Note: You can add multiple MPCs and other tools to the agent. For example, you can add both the WorkPoint 365 MCP and the SharePoint MCP to the same agent.

We can now try testing the agent. In the following images, we ask the agent a series of questions related to projects in our WorkPoint solution: