MCP.Market

eResource Scheduler MCP server

online · 100% uptime
by app.eresourcescheduler.cloud·cloud.eresourcescheduler.app/eresource-scheduler·v1.0.0
No reviews yet

Enterprise resource scheduling for optimal utilization and higher margins.

A97/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed eResource Scheduler yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

eResource Scheduler tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 176ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How eResource Scheduler compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
69 ms
faster than 90% of 30,031 servers

Install eResource Scheduler in Claude Code, Cursor or VS Code

claude mcp add --transport http eresource-scheduler https://app.eresourcescheduler.cloud/mcp
Add to Cursor

What the publisher says

From the eResource Scheduler repository's README, as published. We do not edit it. Read it on GitHub

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.

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=.
  2. mcp-publisher login http --domain app.eresourcescheduler.cloud …
  3. mcp-publisher publish (from a directory containing this server.json).
  4. Email partnerships@github.com 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

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

Example prompts

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

eResource Scheduler: common questions

Is eResource Scheduler MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the eResource Scheduler safety report
How do I install eResource Scheduler?
It runs remotely at app.eresourcescheduler.cloud. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does eResource Scheduler need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is eResource Scheduler maintained?
The last commit was 37 days ago (2026-09-28). The latest release is v1.0.0.
Is eResource Scheduler up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does eResource Scheduler compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 69 ms (faster than 90% of 30,031 servers). Full comparison.