
eResource Scheduler
cloud.eresourcescheduler.appPublished by app.eresourcescheduler.cloudOfficial publisherv1.0.0Updated Oct 24, 2026
Enterprise resource scheduling for optimal utilization and higher margins.
Overview
Remote MCP connector for eResource Scheduler that lets an assistant view and manage resources, projects, bookings, and timesheets under your account permissions
- What you can do
- View and manage resource schedules and availability, including working and non-working exceptions and over-capacity resources. Track projects, bookings, and allocations, including unfilled demand and date shifts. Work with timesheets and related status, such as logging time, submitting, and approving. Run guided skills for daily briefings, utilization and financial reports, and bulk updates across many records.
- When to use it
- Useful when your organization runs resource planning in eResource Scheduler and you want an assistant to answer utilization and availability questions, prepare briefings and reports, or make booking and timesheet changes without leaving the chat.
- Requirements
- An active eResource Scheduler account and completion of the OAuth sign-in prompt when the client connects. A client that supports remote Streamable HTTP MCP, such as Cursor, Claude with plugins, or GitHub Copilot. No API keys or environment variables are declared.
Installation
In SourceWeft
- Open eResource Scheduler in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/cloud.eresourcescheduler.app%2Feresource-scheduler/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"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.
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
- Open Cursor Settings → Plugins.
- Search for eResource Scheduler.
- Click Install, then complete the eRS sign-in prompt.
Or run /add-plugin eresource-scheduler in chat.
Install — Claude
From a local checkout:
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)
- Host
/.well-known/mcp-registry-authonapp.eresourcescheduler.cloudcontainingv=MCPv1; k=ed25519; p=<public key>. mcp-publisher login http --domain app.eresourcescheduler.cloud …mcp-publisher publish(from a directory containing thisserver.json).- 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):
- 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
- Show the overall utilization for this quarter.
- Show resources who are overutilized.
- List all working and non-working exceptions for David this month.
- List all bookings for Ava starting this week or next week.
- 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
- Documentation — Connect eRS to your AI assistant
- Privacy policy
- Terms of service
- Contact support
- Product: https://www.eresourcescheduler.com
- Support email: [email protected]
Repository layout
License
MIT — see LICENSE.
Source: README.md at commit 116e090
Tools
0Version history
1- v1.0.0LatestSep 28, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts