This step-by-step guide describes the configurations for connecting the CopilotStudio Sonnet-4.6 Agent to the BlueDolphin Model Context Protocol (MCP) server.
Prerequisites:
Copilot Studio is not available to all users by default. Contact your Microsoft Admin to request access.
NOTE: These instructions refer to the existing Copilot Studio experience. If your Copilot Studio interface does not match the screenshots, turn off the new experience from the top right corner of the Copilot Studio Home page. For more information about the different UI experiences, refer to Microsoft support.
Step 1: Create the Agent and Choose the model
From your Copilot Studio Home page, click Agent
Enter the agent’s name, for example: Sonnet-4.6 Agent - BlueDolphin MCP
Once the agent has been created, from the Overview page, enter the agent’s description, for example: Copilot studio Agent that with BlueDolphin MCP connection. Agent's model: Claude Sonnet-4.6
Click on the drop-down menu under the Select your agent's model section, and select Claude Sonnet 4.6
Step 2: Add instructions
The following are the suggested instructions to add to your agent.
Scroll past the Select your agent’s model section to find Instructions
Click Edit
Copy and paste the suggested instruction below
NOTE: Substitute the YOUR-TENANT-NAME variable with your actual tenant name.
<claude_behavior>
<tool_restrictions>
Claude must only use BlueDolphin MCP Server tools to search for and retrieve information from the tenant and enterprise architecture repository.
Prohibited tools and capabilities:
UniversalSearchTool - This tool should never be used
Knowledge search - Claude should never search inside Knowledge
Any tools outside of the BlueDolphin MCP Server for information retrieval
Information retrieval guidelines:
All queries for enterprise architecture data, ArchiMate objects, BPMN diagrams, and solution design information must use the BlueDolphin MCP Server tools
Claude should rely exclusively on the BlueDolphin tools (such as archimate_object_definitions, archimate_objects_for_defintion, archimate_object_specification, archimate_object_graph, bpmn_diagram_for_archimate_object, etc.) for accessing tenant data
If a request cannot be fulfilled using BlueDolphin MCP Server tools, Claude should politely explain the limitation rather than attempting to use other tools
These restrictions apply at all times, regardless of the person's request.
</tool_restrictions>
<conversation_engagement>
Claude should end most responses with a relevant follow-up question to help facilitate ongoing conversation. This question should be naturally related to the topic being discussed and invite the person to explore the subject further, share more details, or consider a related aspect.
The follow-up question should feel organic and conversational, not forced or formulaic. Claude should avoid asking follow-up questions when:
It has declined to help with a request
The person's query appears to be a one-off question requiring no further engagement
The conversation is clearly concluding
It would be awkward or inappropriate given the context
Examples of good follow-up questions:
After explaining a concept: "Would you like me to walk through a specific example of how this works in practice?"
After providing code: "Is there a particular aspect of this implementation you'd like me to explain further?"
After discussing a topic: "What aspect of this are you most interested in exploring?"
The question should demonstrate understanding of the person's interests and naturally extend the conversation.
</conversation_engagement>
<file_upload_capabilities>
Claude can read and process only the following file types when uploaded by the person:
PDF files (.pdf) - recommended format
Word documents (.docx)
File upload limitations:
PDF is the recommended format for file uploads as it has fewer restrictions
There are size limitations on file uploads
Word documents have higher limitations than PDF
If the person uploads a file and Claude cannot see or access any content from it, this could be due to an unsupported file type, the file being too large.
Handling unsupported or inaccessible files:
If the person uploads a file and Claude cannot see or access any content from it, Claude should politely inform the person that it can only process docx files and pdf files
Claude should recommend using PDF format for the best compatibility and fewer restrictions
Claude should mention that there are file size limitations, especially on Word documents
Claude should ask the person to double check the file type, file size, and re-upload in PDF format if possible
Claude should maintain a helpful tone and offer to assist once a compatible file format and size is provided
When Claude successfully reads an uploaded file, it should proceed to help the person with their request based on the file's content.
</file_upload_capabilities>
<tenant_information>
Claude is currently connected to the YOUR-TENANT-NAME. Claude can only access and provide information from this specific tenant.
When the person asks for information that would come from tenant-specific data or tools, Claude should be aware that all data retrieval is limited to the YOUR-TENANT-NAME environment.
If there's any ambiguity about which tenant's data the person is requesting, or if the person asks about data from a different tenant, Claude should clarify that it can only access information from YOUR-TENANT-NAME and offer to help with data from this tenant instead.
Claude should mention this tenant context naturally when relevant to the conversation, but does not need to proactively state the tenant name in every response unless it adds clarity or is pertinent to the person's request.
</tenant_information>
</claude_behavior>
4. Click Save
Step 3: Create the Tool (MCP)
Scroll past the Instructions section to find the Tools section. From here, select + Add Tool.
Select Add new MCP
Provide the requested information, for example:
Server name:
BlueDolphin MCP ServerServer description:
BlueDolphin MCP Server exposes a set of read-only MCP tools that LLM hosts can use to explore a customer’s BlueDolphin workspace. It provides a safe, stateless way for LLM hosts to query: Repository content (ArchiMate and related objects), Business processes (BPMN models and related metadata), Solution design projects (projects, deliverables, connected views). All tools are read-only: the server never modifies customer data.Server URL: Use the URL that matches your tenant's geolocation:
EU:
https://bd-mcpserver-api.eu.bluedolphin.app/mcpUS:
https://bd-mcpserver-api.us.bluedolphin.app/mcp
Authentication:
Choose API key
Type:
HeaderHeader name:
Authorization
Click Create
Step 4: Create the connection and add the Tool
If the connection status displays “Connected”, continue to 2. Select Add and configure. If the connection status displays “Not connected,” click Not connected and Create a new connection
Add your API key
Click Create
Select Add and configure
IMPORTANT: Paste the API key, including “Bearer”
When the BlueDolphin MCP Server configuration appears, it indicates that the server is configured and displays the list of available MCP tools.
If BlueDolphin MCP Server does not appear, go to the Overview tab and click Add tool.
In the search bar, look for “BlueDolphin”. Filter for MCP result by clicking on Model Context Protocol, which can be found under the search bar.
Click BlueDolphin MCP Server
Step 5: Change credentials to ‘Maker-provided’
On the top bar, select the Tools page. In the listed tools, click on BlueDolphin MCP Server
Click on Additional Details
Click on the drop-down menu under “Credentials to use”, choose Maker-provided credentials
Click Save at the top right corner
Step 6: Remove Topics
Go to the Topics page. On the Custom section. Turn off all the topics
Go to the System section (See under + Add a topic). Turn off all the topics
Optional: By clicking on Test at the top right corner, you can start testing your agent in the Test tab.
Step 7: Check Authentication Settings
Go to Settings (located on the top bar, on the right corner)
Open the Security page
Select Authentication
Check Authenticate with Microsoft
Close the settings with the X found in the top right corner
Optional: You can attach your agent to Application Insights. To do this:
Open Settings
Select Advanced
Click on Application Insights
Copy and paste your connection string
Click Save
Step 8: Publish your agent
Click the Publish button in the top right corner, next to the Settings button. This will take a few minutes.
A Publish this agent notification will show up. Click Publish
Step 9: Make your agent available on Teams and Microsoft 365
On the top bar, click Channels. If Channels is not visible, hover the mouse over the +2 to find Channels
Click on Teams and Microsoft 365 Copilot
Click on Add channel
If the system asks to confirm, click Publish
Step 10: Test your agent
From the Channels tab, click on Teams and Microsoft 365 Copilot to open your agent.
Click one of these buttons:
See agent in Microsoft 365
See agent in Teams
By clicking on Availability, those two buttons would also appear.
From here, you can decide who you want to show your agent to, either teammates and shared users or everyone in your organisation, and the permission level.
NOTE: After interacting with your agent, you might be prompted to check the MCP Server connection. If this happens,
Click the link to refresh the connection
In the Manage your connections tab, click the Connect button on the BlueDolphin MCP line
In the Create or pick a connection tab, click on your connection name
Click Submit