Skip to main content

How to Connect eRS to Other MCP-Compatible Clients: Step-by-Step Guide

  • Updated

The eResource Scheduler MCP server lets you work with your eRS data from any MCP-compatible AI assistant or developer tool. Setup takes about 5 minutes: an eRS admin enables the MCP server once, then each user adds eRS to their own client.

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 client signs in as you, so it can only see and do what your eRS access rights allow.
  • An MCP client that supports remote Streamable HTTP servers with OAuth, or can run mcp-remote through npx.

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 an MCP client.

MCP Server enabled, with the endpoint URL and copy button

 

Part B: Add eResource Scheduler to Your MCP Client (Each User)

Step 1. Add eRS as a remote MCP server

In your client's MCP settings, add a new server with these settings:

  • Transport: Streamable HTTP
  • Server URL: https://app.eresourcescheduler.cloud/mcp
  • Authentication: OAuth

Step 2. Use mcp-remote if your client needs it

If your client can't connect to remote servers directly and uses mcp-remote instead, use:

  • Command: npx
  • Arguments: -y mcp-remote https://app.eresourcescheduler.cloud/mcp
  • Environment: None

Step 3. Sign in to eRS

When your client prompts you to authenticate, complete the eRS sign-in.

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.

eResource Scheduler login page

Step 4. Confirm the connection

Check that eResource Scheduler shows as connected in your client and that its tools are listed. Some clients only load MCP tools after a restart.

 

Start Using eRS in Your Client

Open a new chat in your client 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:

 

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.