Dotwork MCP: Microsoft Copilot Studio

Dotwork exposes a Streamable MCP server that Microsoft Copilot Studio can use to discover and invoke Dotwork tools.

This is a customer-configured, bring-your-own MCP integration. Dotwork does not need to be a certified Microsoft partner for a private customer deployment. Microsoft certification and Partner Center verification are only required for broadly publishing a certified MCP server through Microsoft discovery surfaces.

Prerequisites

Before connecting Dotwork, confirm:

The Dotwork MCP endpoint is reachable from Microsoft Copilot Studio.
Customer firewall, WAF, and reverse-proxy policies permit the connection.
Dotwork OAuth discovery and authorization endpoints are reachable.
The connecting user has access to at least one Dotwork site.
The Power Platform environment allows the MCP connector under its data-loss-prevention policies.

Dotwork endpoint

https://<dotwork-host>/ai/mcp

The edge configuration must also allow the OAuth discovery and authorization routes used during connection setup, including:

Category	Endpoint
Well-Known	`/.well-known/oauth-protected-resource/ai/mcp`
Well-Known	`/.well-known/oauth-authorization-server/ai/mcp`
OAuth	`/ai/oauth/register`
OAuth	`/ai/oauth/authorize`
OAuth	`/ai/oauth/authorize/callback`
OAuth	`/ai/oauth/authorize/complete`
OAuth	`/ai/oauth/token`

The Dotwork sign-in page must also be reachable during the interactive authorization flow.

Add Dotwork to Copilot Studio

Open the target agent in Microsoft Copilot Studio.
Go to Tools.
Select Add a tool.
Select New tool.
Select Model Context Protocol.
Enter the server details:
- Server name: Dotwork
- Server description: Read and analyze structured work data, relationships, status, and workflows in Dotwork.
- Server URL: https://<dotwork-host>/ai/mcp
Select OAuth 2.0 for authentication.
Select Dynamic discovery.
Select Create.
Create a new connection when prompted.
Sign in to Dotwork.
If the user can access multiple Dotwork sites, select the site that should be associated with the connection.
Return to Copilot Studio and select Add to agent.

Dynamic discovery is preferred because Dotwork exposes OAuth authorization-server metadata, protected-resource metadata, PKCE support, and dynamic client registration.

Configure the available tools

Copilot Studio initially enables all tools advertised by an MCP server.

For a controlled rollout:

Open the Dotwork MCP tool in the agent’s Tools page.
Turn off Allow all.
Enable only the tools required by the agent.
Save the agent configuration.

When Allow all is off, newly added MCP tools are disabled by default.

Dotwork also applies server-side controls:

Per-site mcp.disabled_tools policy
Write-tool feature gates
Question and Skill tool feature gates
Site-scoped custom-tool visibility

A tool must therefore be enabled by both Dotwork policy and the Copilot Studio agent configuration.

Recommended pilot tool set

Start with read-only tools such as:

environment_get_context
site_get_spaces
site_get_ontology
site_get_artifact_kind_contexts
space_get_artifact_kind_contexts
artifact_get_kinds
field_get_available
field_get_details
query_artifacts
aggregate_artifacts
artifact_get_specific
artifact_status_updates_get
relationship_get_nodes
relationship_get_item_tree
workflow_list

Validate the connection

After adding Dotwork, test the following prompts.

Environment context

What Dotwork site is this connection using?

Expected behavior:

Copilot invokes environment_get_context.
The response identifies the selected Dotwork site.

Workspace structure

Show me the spaces and artifact types available in this Dotwork site.

Expected behavior:

Copilot invokes the site or Space discovery tools.
The response reflects only data available to the authenticated user.

Artifact search

Find the five highest-priority items in any space.

Expected behavior:

Copilot resolves the Space, artifact kind, and relevant fields.
Copilot invokes query_artifacts.
Results respect Dotwork authorization and site scope.

Aggregation

Count Objectives by status across the site.

Expected behavior:

Copilot invokes aggregate_artifacts.
The response contains grouped counts rather than a client-side count of paginated records.