Connect Procore to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Procore, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Procore + Microsoft Copilot

Read Procore construction projects: companies, projects and directory, RFIs and submittals, daily and manpower logs, project documents and files, budget views and line items, subcontracts and purchase orders. OAuth 2.0, read-only.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

PROCORE_CLIENT_ID, PROCORE_CLIENT_SECRET

Step 1 — Get credentials

The connector reads Procore through OAuth 2.0 and only reads. Every call runs as the Procore user who authorized it and sees what that user sees.

1. At https://developers.procore.com sign in, click Create New App and add an OAuth credential of type Web server application. Set the redirect URI to <your AnythingMCP URL>/api/mcp-oauth/callback (on AnythingMCP Cloud: https://cloud.anythingmcp.com/api/mcp-oauth/callback).
2. Copy the production client ID and client secret into PROCORE_CLIENT_ID and PROCORE_CLIENT_SECRET.
3. A Procore company administrator installs the app in the company (Company Admin > App Management > Install Custom App, with the app's version key). Without that, the company's data is not reachable.
4. On the connector page click Authorize with Provider and sign in to Procore. Tokens are refreshed automatically.
5. Start with procore_list_companies for the company id, then procore_list_projects. Every company-scoped tool takes company_id; without it Procore answers 400.

Things to know:

• A 403 means the user's permission template lacks access to that tool (RFIs, Budget, Documents) on the project. Budget and commitment tools need the Financials tools enabled on the project.
• Lists return 100 items per page; pass page and per_page.
• The rate limit is 3,600 requests per hour per app and user; a 429 says when to retry.
• To test against a developer sandbox, change the base URL and the OAuth URLs in the connector settings to https://sandbox.procore.com and https://login-sandbox.procore.com.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Procore tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse