Configuring Pinpoint MCP in Microsoft Copilot Studio (Manual Method)

Manual Method


πŸ“˜

There is a more reliable way of setting up the Pinpoint MCP. If you have access to creating custom connectors in Power Apps or Power Automate we recommend checking our recommended method.

This guide walks through manually adding the Pinpoint ATS MCP server as a tool in a Copilot Studio agent.

Prerequisites


Step 1 β€” Create or open an agent

In Copilot Studio, go to Agents in the left navigation. You can either open an existing agent or create a new one by clicking Create blank agent in the top right.

Step 1 – Agents page with Create blank agent highlighted

Step 2 β€” Open the Add tool dialog

Once inside the agent, scroll down to the Tools section and click Add tool.

Step 2 – Agent overview showing the Add tool option

Step 3 β€” Select Model Context Protocol

In the Add tool dialog, click Add new MCP (or select the Model Context Protocol tab and choose that option).

Step 3 – Add tool dialog with MCP option visible

Step 4 β€” Fill in the MCP server details

Complete the Model Context Protocol form with the following values, then click Create:

FieldValue
Server namePinpoint ATS
Server descriptione.g. Pinpoint ATS API MCP – exposes tools to analyse Pinpoint ATS API documentation and execute API calls.
Server URLhttps://developers.pinpointhq.com/mcp
AuthenticationAPI key
TypeHeader
Header namex-api-key
Step 4 – Model Context Protocol form filled in

Step 5 β€” Review the created tool

After clicking Create, you will see a confirmation that the Pinpoint ATS custom connector has been created. The tool preview shows the description and a Connection section. Click Add and configure to proceed.

Step 5 – Tool created confirmation

Step 6 β€” Create a new connection

The connection status shows Not connected. Click the Connection dropdown and select Create new connection.

Step 6 – Connection dropdown with Create new connection option

Step 7 β€” Enter your API key

A Connect to Pinpoint ATS dialog appears. Paste your Pinpoint API key into the field and click Create.

Step 7 – Connect to Pinpoint ATS dialog with API key field

Step 8 β€” Confirm the connection and add the tool

The connection will show as Pinpoint ATS β€” connected. Click Add and configure to add the tool to your agent.

Step 8 – Connection established, ready to add

Step 9 β€” Verify the tool appears in your agent

Back on the agent overview, you should now see Pinpoint ATS listed under the Tools section.

Step 9 – Pinpoint ATS tool visible in agent Tools section

Step 10 β€” Add the required agent instructions

Click Edit next to the Instructions field and add the following text, replacing <your-subdomain> with your Pinpoint instance subdomain:

When using the Pinpoint MCP tool to call the Pinpoint API, use '<your-subdomain>' as a subdomain for the API request and add 'X-Original-Host: <your-subdomain>.pinpointhq.com' header to the 'execute-request' tool parameters.

For example, if your Pinpoint URL is acme.pinpointhq.com, your subdomain is acme. Make sure to replace both occurrences!

Click Save when done.

Step 10 – Instructions field with the required MCP instruction text

Step 11 β€” Test the agent

In the Test your agent panel on the right, type a prompt such as:

Get the 3 latest applications from Pinpoint

The agent will respond that it needs to establish a connection first, and will show an Open connection manager link.

Step 11 – Agent prompts user to open connection manager

Step 12 β€” Open the connection manager

Click Open connection manager. This opens the Manage connections page in a new tab, where Pinpoint ATS is listed as Not Connected. Click Connect.

Step 12 – Manage connections page showing Pinpoint ATS Not Connected

Step 13 β€” Submit the connection

A Create or pick a connection dialog appears with Pinpoint ATS listed and showing a connected status. Click Submit.

Step 13 – Create or pick a connection dialog, click Submit

Step 14 β€” Retry the request

Return to your agent tab. Click Retry in the test panel.

Step 14 – Agent panel showing Retry button

Step 15 β€” Done

The agent now successfully retrieves data from Pinpoint. You can see application details returned from the Pinpoint API, including Application ID, email, phone, stage, channel, country, and internal candidate flag.

Step 15 – Successful response showing Pinpoint application data