Contents
Setup Copilot for Users
To add SigParser to Microsoft Copilot as a custom MCP you'll need to do the following:
Go to Microsoft Admin Center
Go to Copilot -> Connectors -> Find "Create a new connector" and click "Add"
It can be hard to find the "Create a new connector" becuase it's under the Recommended section as of 8/19/2026
Click Add for Connect to MCP Server
Add a custom MCP
Display Name: SigParser MCP
MCP endpoint URL: https://ipaas.sigparser.com/api/mcp
Authentication: OAuth 2.0 with Dynamic Client Registration (DCR)
If not available, choose OAuth 2.0 and do the steps below for configuring the Microsoft Teams OAuth 2.0 flow. Then fill in the Reference ID.
Check the checkbox for the Notice
Click Create
You'll be asked to then provide a Description:
SigParser is a database of Contact, Company and Relationship data derived from email and meeting data. Use SigParser MCP when trying to find out how well you or your firm know another contact or company. It's also useful for finding contact data such as names, email addresses, job titles, locations and phone numbers
Wait 5 minutes
Open Microsoft Copilot on your computer and go to Settings (gear icon) and then Settings
Start a chat (be sure to enable Work IQ) by asking a simple question like "Fetch some Contacts from the SigParser MCP".
Configure OAuth for SigParser for Microsoft Teams
If your Microsoft acocunt doesn't support Dynamic Client Registration then you'll need to do this step which is annoying but needed until Microsoft fully rolles out Dynamic Client registration for MCP endpoints.
Easiest way to do this is the following by asking an AI tool like Claude Code or ChatGPT to do the following to generate the values you need.
I need to connect SigParser to Microsoft 365 Copilot as a custom federated connector.
Please generate an OAuth client for me and give me the exact values to paste into the
Microsoft Teams Developer Portal.
STEP 1 - Company name
Before doing anything else, check whether I have told you my company name in this
conversation. If I have not, stop and ask me: "What is your company name?" Do not proceed
or guess. The company name is required because it goes into the OAuth client name so
SigParser can tell registrations apart.
STEP 2 - Look up the current endpoints
Fetch this URL and read the JSON:
https://app.sigparser.com/.well-known/oauth-authorization-server
Record the values of "authorization_endpoint", "token_endpoint", and "registration_endpoint".
If that request fails, use these known values instead:
authorization_endpoint = https://app.sigparser.com/Home/Login
token_endpoint = https://app.sigparser.com/api/Ipaas/token
registration_endpoint = https://app.sigparser.com/oauth/register
STEP 3 - Register the OAuth client
Send a single POST request to the registration_endpoint from step 2. No authentication
header is needed.
Method: POST
Header: Content-Type: application/json
Body:
{
"client_name": "<MY COMPANY NAME> - Microsoft 365 Copilot",
"redirect_uris": ["https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect"],
"grant_types": ["authorization_code"],
"response_types": ["code"],
"token_endpoint_auth_method": "client_secret_post",
"scope": "all"
}
Replace <MY COMPANY NAME> with my actual company name from step 1. Keep the rest exactly
as written. The redirect URI is Microsoft's and must not be changed.
Send this request only once. Every call creates a new client record. If it fails, show me
the error and ask before retrying.
The response will contain "client_id" and "client_secret".
STEP 4 - Give me the output in exactly this format
Print the block below with the blanks filled in, nothing rearranged, nothing renamed:
Registration name: SigParser OAuth
Base URL: https://ipaas.sigparser.com
Restrict usage by organization: My organization only
Restrict usage by Teams app: Any Teams app (for testing and store validation only)
Client ID: <client_id from step 3>
Client Secret: <client_secret from step 3>
Authorization endpoint: <authorization_endpoint from step 2>
Token endpoint: <token_endpoint from step 2>
Refresh endpoint: [leave blank]
Scope: all
Enable Proof Key for Code Exchange (PKCE): Yes
Client password authentication method: Request body parameters (default)
After the block, add one short warning: the client secret is a credential, so I should
store it in a password manager and not paste it into email or chat.
If you cannot make web requests, do not invent any values. Instead, give me a ready-to-run
curl command and a Postman setup for the step 3 request, and tell me to bring the response
back to you so you can format it.Or you can do these steps manually by generating the client and secret by making a POST request to the register URL then fill in the form like so
Registration name: SigParser OAuth
Base URL: https://ipaas.sigparser.com
Restrict usage by organization: My organization only
Restrict usage by Teams app: Any Teams app (for testing and store validation only)
Client ID:
Client Secret:
Authorization endpoint: https://app.sigparser.com/Home/Login
Token endpoint: https://app.sigparser.com/api/Ipaas/token
Refresh endpoint: [leave blank]
Scope: all
Enable Proof Key for Code Exchange (PKCE): Yes
Client password authentication method: Request body parameters (default)Open the create page OAuth flow in Microsoft Teams
Copy and paste each value into the page.
Save
Copy the reference ID and use it on the MCP connector setup screen
FAQ: Write actions only work in Cowork
A common source of confusion is trying to use the write actions like Enrich Contact, Send to Connector or Update Contact through the MCP Copilot connector in the Chat mode.
You can only use these in the Cowork mode in Copilot app. The Cowork mode does require having available credits for your employees to use. You can configure credits here.
Microsoft Instructions:
SigParser MCP Server URL:
More Info:


