mcpField
E
eResource Scheduler

eResource Scheduler

Remote
eresourcescheduler.comProductivity0Updated 4w ago

About eResource Scheduler

eResource Scheduler connects enterprise resource scheduling to AI clients for teams managing people, projects, and time. Clients can work with schedules, bookings, projects, and timesheets under the authorizing account’s permissions, and run guided workflows.

Key features

  1. 01View and manage schedules and availability
  2. 02Track projects, bookings, and allocations
  3. 03Work with timesheets and their status
  4. 04Run briefing, reporting, and bulk-update workflows

Use cases

  1. 01Review team utilization and over-capacity
  2. 02Check resource bookings and availability
  3. 03Enter and submit project timesheets
  4. 04Bulk-update or archive records

MCP support

A remote Streamable HTTP MCP server connects to eResource Scheduler using OAuth 2.0. Clients act with the authorizing user’s permissions and can access only data available to that user.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://app.eresourcescheduler.cloud/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project 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

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

From a local checkout:

claude plugin marketplace add ./path/to/eRS-MCP
claude 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):

{
  "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

.
├── .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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.