Skip to main content

How to Connect eRS to GitHub Copilot: Step-by-Step Guide

  • Updated

The eResource Scheduler MCP server lets you work with your eRS data from GitHub Copilot. Setup takes about 5 minutes: an eRS admin enables the MCP server once, then each user adds eRS as an MCP server in their own GitHub Copilot settings.

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. GitHub Copilot signs in as you, so it can only see and do what your eRS access rights allow.
  • GitHub Copilot, with access to its Customize settings to add an MCP server.

Important: eRS passwords, API keys, and access tokens should never be pasted into a client configuration file. Authentication happens through eRS OAuth in the browser, not through pasted credentials.

 

Part A: Enable the MCP Server in eResource Scheduler (Admin, One Time)

Skip to Part B 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.

eRS user menu with Administration option

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.

MCP Server page with the toggle set to Disabled

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 GitHub Copilot.

MCP Server enabled, with the endpoint URL and copy button

 

Part B: Add eResource Scheduler to GitHub Copilot (Each User)

Step 1. Open Customize

Open Settings and select Customize, then click Go to Customize.

Settings with Customize and Go to Customize highlighted

Step 2. Add an MCP server

Click Add at the top right and select MCP Server.

Customize page with Add and MCP Server highlighted

Step 3. Enter the eRS details

Enter the server name eResource Scheduler MCP and select HTTP as the type. Enter the URL https://app.eresourcescheduler.cloud/mcp and click Save. The other fields are optional.

MCP server configuration with the name, HTTP type and URL highlighted

Step 4. Sign in to eRS

Go to the MCP tab in Customize. Under Installed, click Sign in next to eResource Scheduler.

Installed MCP servers with eResource Scheduler and the Sign in button

Step 5. Complete sign-in and confirm the connection

The eRS login page opens in your browser. Enter your eRS Login ID and password and click Login, or click Single Sign On if your company uses SSO.

Back in GitHub Copilot, eResource Scheduler shows a green check and its toggle is on.

eResource Scheduler login page

eResource Scheduler shown as connected

 

Start Using eRS in GitHub Copilot

Open a new chat in GitHub Copilot and ask about your schedule in plain language. Mentioning "eResource Scheduler" in your first request helps Copilot pick the right tools. 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:

 

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.