Connect Phorest to Microsoft Copilot via MCP

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

Phorest + Microsoft Copilot

Phorest salon and spa software: branches, staff and timetables, services and categories, clients with service and product history, appointments, free appointment slots, products and stock, gift vouchers and reviews. Phorest Third Party API with Basic auth; bookings and client creation are included but installed switched off.

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:

PHOREST_API_URL, PHOREST_BUSINESS_ID, PHOREST_USERNAME, PHOREST_PASSWORD

Step 1 — Get credentials

The connector uses the Phorest Third Party API with HTTP Basic auth. Every call is scoped to one business, and most to a branch.

1. Phorest grants API access on request: open an "API access" ticket at https://support.phorest.com from an e-mail address registered on your business, with your Phorest account number.
2. Phorest sends a username and a password. Keep the global/ prefix of the username (for example global/[email protected]) and put them into PHOREST_USERNAME and PHOREST_PASSWORD.
3. Put the business id that comes with the credentials into PHOREST_BUSINESS_ID. If it is missing, ask [email protected].
4. Set PHOREST_API_URL to https://api-gateway-eu.phorest.com for Europe or https://api-gateway-us.phorest.com for the United States, Canada and Australia. A US account on the EU host answers 401.
5. Start with phorest_list_branches for the branchId that the other tools take as branch_id.

Things to know:

• The API works on the live salon data. phorest_create_client, phorest_create_booking and phorest_cancel_appointments are installed switched off; turn them on only if you want them.
• Date ranges for appointments and staff timetables are limited to one month (from_date and to_date as yyyy-MM-dd).
• Paging: page starts at 0, size goes up to 200 (1000 for staff timetables).
• The API offers no webhooks and no card payments; use the updated_from filters to pick up changes.

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 Phorest 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