eResource Scheduler

cloud.eresourcescheduler.appv1.0.0Updated Sep 28, 2026

Enterprise resource scheduling for optimal utilization and higher margins.

VerifiedStreamable HTTPWeb executableOther

Overview

AI-generated overview

Connect an assistant to eResource Scheduler to view and manage resources, projects, bookings, and timesheets.

What it does
A remote MCP server that links an AI client to an eResource Scheduler account, exposing schedules, resources, projects, bookings, allocations and timesheets. It offers guided skills for setup, workspace building, daily briefings, reports (utilization, availability, financials, forecast, progress), booking and allocation changes, timesheet logging and approval, and bulk record hygiene including archiving and deletion. Actions run as the eRS user who authorizes the connection, so the client only reaches data that user can access.
When to use it
Useful for resource managers and project teams who already run eResource Scheduler and want to query utilization, over-allocation and pending timesheets, or make booking and timesheet changes conversationally instead of through the web app.
Requirements
An active eResource Scheduler account, completion of an OAuth 2.0 sign-in when prompted, and an MCP client that can load remote Streamable HTTP MCP servers (for example Cursor, Claude with plugins, or GitHub Copilot); the endpoint is hosted by the provider, so network access is required.
Before you install
Signing in delegates access to the assistant as your eRS user, so it can create, update, archive and delete records, submit or approve timesheets, and apply bulk changes wherever your account permits. All requests go to the vendor's hosted service under its own privacy policy and terms, and data is limited to what your account can already see; review the OAuth grant and revoke it when no longer needed.

Installation

In SourceWeft

  1. Open eResource Scheduler in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "eresource-scheduler": {
      "type": "http",
      "url": "https://app.eresourcescheduler.cloud/mcp"
    }
  }
}

README

eResource Scheduler

Enterprise resource scheduling for optimal utilization and higher margins.

Connects eResource Scheduler to AI clients via a remote MCP server. After you install and sign in, the client can work with your schedules, resources, projects, bookings, and timesheets using your account permissions.

CategoryProductivity
PublisherEnbraun Technologies Private Limited
Plugin IDeresource-scheduler
Display nameeResource Scheduler
Claude marketplaceeresource-scheduler
MCP Registry namecloud.eresourcescheduler/eresource-scheduler

What you can do

  • View and manage resource schedules and availability
  • Track projects, bookings, and allocations
  • Work with timesheets and related status
  • Run guided skills for briefing, reports, bookings, and bulk updates

Actions run as the eRS user who authorizes the connection. Clients only use data that user can access.

Requirements

  • An active eResource Scheduler account
  • Ability to complete OAuth sign-in when prompted
  • One of: Cursor, Claude (with plugins), or an MCP client that can load Official MCP Registry remotes (e.g. GitHub Copilot)

Install — Cursor

  1. Open Cursor Settings → Plugins.
  2. Search for eResource Scheduler.
  3. Click Install, then complete the eRS sign-in prompt.

Or run /add-plugin eresource-scheduler in chat.

Install — Claude

bash
claude plugin marketplace add enbraun-org/eRS-MCPclaude plugin install eresource-scheduler@eresource-scheduler

From a local checkout:

bash
claude plugin marketplace add ./path/to/eRS-MCPclaude plugin install eresource-scheduler@eresource-scheduler

Then enable the plugin and complete the eRS sign-in prompt when Claude connects to the MCP server.

Install — GitHub Copilot / MCP Registry

Listing metadata lives in server.json (Official MCP Registry). Clients that support remote Streamable HTTP MCP (including GitHub Copilot) discover the connector from the registry, then connect to:

https://app.eresourcescheduler.cloud/mcp

Publish (outside this repo)

  1. Host /.well-known/mcp-registry-auth on app.eresourcescheduler.cloud containing v=MCPv1; k=ed25519; p=<public key>.
  2. mcp-publisher login http --domain app.eresourcescheduler.cloud …
  3. mcp-publisher publish (from a directory containing this server.json).
  4. Email [email protected] for GitHub MCP Registry curation.

Do not commit key.pem.

MCP

Root Cursor connector (mcp.json), Claude bundled connector (plugins/ers/.mcp.json), and Registry remote (server.json):

json
{  "mcpServers": {    "eresource-scheduler": {      "type": "http",      "url": "https://app.eresourcescheduler.cloud/mcp"    }  }}
  • Transport: Streamable HTTP (remote)
  • Auth: OAuth 2.0 against eResource Scheduler
  • Endpoint: the eRS app MCP URL

Skills

SkillWhat it does
setupConnect, first run, what MCP can and cannot do
workspace-builderCreate people, equipment, projects, and tasks from scratch
daily-briefingToday’s free/busy, over capacity, and pending timesheets
reportsUtilization, availability, financials, gap, forecast, progress, timesheet report
booking-allocationBook, unfilled demand, split, shift dates
timesheet-workflowLog time, copy from schedule, submit/approve
bulk-hygieneSame change on many records, archive, mass create, delete

Shared rules: plugins/ers/skills/shared-patterns.md.

Example prompts

  1. Show the overall utilization for this quarter.
  2. Show resources who are overutilized.
  3. List all working and non-working exceptions for David this month.
  4. List all bookings for Ava starting this week or next week.
  5. Henry, Ava, and Lucas have worked 4 hours on Cobalt Mobile App every day this week. Enter and submit their timesheets.

Privacy, docs, and support

Repository layout

text
.├── .cursor-plugin/plugin.json               # Cursor marketplace manifest├── mcp.json                                 # Cursor MCP connector├── .claude-plugin/marketplace.json          # Claude marketplace catalog├── server.json                              # Official MCP Registry / Copilot├── assets/logo.png                          # Plugin logo└── plugins/ers/    ├── .claude-plugin/plugin.json           # Claude plugin manifest    ├── .mcp.json                            # Claude MCP connector    └── skills/                              # Shared agent skills

License

MIT — see LICENSE.

Source: README.md at commit 116e090

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestSep 28, 2026