The eResource Scheduler MCP server lets you work with your eRS data inside agents you build in Microsoft Copilot Studio. Setup takes about 10 minutes: an eRS admin enables the MCP server once, then an agent maker adds eRS as an MCP tool to their Copilot Studio agent.
Before You Start
You will need:
- An eRS administrator to turn on the MCP server (Part A). This is done once per account.
- Your own eRS login. The connection signs in as you, so the agent can only see and do what your eRS access rights allow.
- A Microsoft Copilot Studio account, with generative orchestration enabled in the agent.
Watch the Video
Prefer to watch? This video walks through the full setup in the new Copilot Studio experience. Prefer written steps? Follow Part A, then Part B (new UI) or Part C (classic) below.
Part A: Enable the MCP Server in eResource Scheduler (Admin, One Time)
Skip to Part B (new UI) or Part C (classic) if your admin has already enabled it and shared the endpoint URL.
Step 1. Open Administration
Log in to eResource Scheduler. Click your name in the top-right corner, then click Administration.
Step 2. Turn on the MCP Server
In the left menu, under INTEGRATION, click MCP Server. Switch the toggle at the top right from Disabled to Enabled. By enabling it, you agree to the MCP Server terms in the Terms of Service.
Step 3. Copy the endpoint URL
Once enabled, the page shows the Endpoint URL: https://app.eresourcescheduler.cloud/mcp. Click the copy icon next to it. Share this URL with anyone in your team who will connect Copilot Studio.
Part B: Add eResource Scheduler to a Copilot Studio Agent (New UI)
Follow these steps if you use the new Copilot Studio experience, as shown in the video. Using the classic experience? Go to Part C.
Step 1. Create an agent
In Microsoft Copilot Studio, go to Agents and click New agent (or Create your first agent).
Step 2. Describe the agent and open Tools
Enter a name, for example eResource Scheduler, and instructions describing what the agent does. Then click + next to Tools.
Step 3. Add an MCP tool
Click Add, then select Model Context Protocol (MCP).
Step 4. Enter the eRS server details
Fill in the Add MCP server form:
| Field | What to enter |
|---|---|
| Server name | eResource Scheduler |
| Server description | A short description, for example: Schedule resources, add & update bookings, log and submit time entries, create dashboards and more. |
| Server URL | https://app.eresourcescheduler.cloud/mcp |
| Authentication | OAuth 2.0 |
| Configuration type | Dynamic (with discovery) |
Click Add.
Step 5. Create a connection
In Select a connection, click the Not connected dropdown and select Create new connection.
Step 6. Sign in to eRS
Click Create. When the eRS login page opens, sign in with your eRS Login ID and password, or click Single Sign On. Back in Copilot Studio, click Add to add the tool to your agent.
Step 7. Test the agent
Go to Preview and test the agent with a sample prompt, for example: "List Project Apollo's details."
Step 8. Add channels and publish
Under Channels, add where the agent should be available, such as Teams + Microsoft 365. Then click Publish and share the agent with your team.
Part C: Add eResource Scheduler to a Copilot Studio Agent (Classic / Standard Agent)
Use these steps instead of Part B if the new-experience toggle is off in Copilot Studio.
Step 1. Create a blank agent
Open Microsoft Copilot Studio and click Create blank agent. Enter a name, for example eResource Scheduler, and click Create.
Step 2. Add a tool
Wait for the agent to finish provisioning (status shows Ready). Go to the Tools tab and click Add a tool.
Step 3. Add a new MCP
Select Add new MCP.
Step 4. Enter the eRS server details
Enter the server name (eResource Scheduler MCP), a description and the server URL https://app.eresourcescheduler.cloud/mcp. Set Authentication to OAuth 2.0 and Type to Dynamic discovery, then click Create.
Step 5. Create a connection
Click the Not connected dropdown, select Create new connection and sign in to eRS when prompted. Then click Add.
Step 6. Test the agent
In the test pane, enter a query, for example: "List Project Apollo's details." If the agent asks you to connect, click Open connection manager, create the connection, then click Retry.
Step 7. Publish and share
Go to Channels and add the channels to publish to, such as Microsoft 365 and Teams. Then click Publish and share the agent with your team.
Start Using eRS in Your Agent
Open your published agent in Teams or Microsoft 365 Copilot, or use the Preview pane in Copilot Studio, and ask about your schedule in plain language. Some prompts to try:
- "Using eResource Scheduler, show me who is booked on Project B next week."
- "What is the team's utilization this month by primary role?"
- "Which resources are free for 3 days next week?"
- "Book Grace Jonas on Project D at 50% from 5 to 9 October."
- "List timesheets waiting for my approval."
Learn More
Once connected, use these guides to see what you can ask:
- Ask AI Assistant About Your Reports
- Ask AI Assistant About Your Resources
- Ask AI Assistant About Your Projects
- Ask AI Assistant About Your Schedule
- Ask AI Assistant About Rates
- Ask AI Assistant About Your Timesheets
- eRS MCP Server: Tools & Prompting Guide
Troubleshooting
| Issue | What to check |
|---|---|
| Authentication failed | Confirm sign-in used an active eRS account, and that the OAuth flow completed fully in the browser without being closed early. |
| Connection failed | Confirm the endpoint URL is exactly https://app.eresourcescheduler.cloud/mcp, including the /mcp path, and that the client supports remote Streamable HTTPS servers. |
| Tools not appearing | Restart the AI client after saving the configuration. Some clients only load MCP tools on startup. |
| Assistant says it can't perform an action | Check the eRS role's permissions for that entity. The MCP server only allows what the account is permitted to do in eRS. |
| Assistant says MCP is disabled | Check with the eRS admin on whether MCP has been enabled. |
Note: Admin-related settings, such as Resource, Project, Booking, Requirement, and Timesheet profiles, along with calendar changes and user rights, can take up to 10 minutes to reflect through the eRS MCP Server. eRS also doesn't control how a connected AI client stores or uses retrieved data, so it's worth checking that client's own data retention and training settings wherever this matters to the organization.