
WIT Calendar
dev.witccPublished by witcc.devOfficial publisherv1.0.0Updated Nov 8, 2026
Unofficial Wentworth (WIT) course catalog and student schedule. Needs a WIT sign-in.
Overview
Unofficial Wentworth (WIT) course catalog and student schedule server, letting an assistant look up courses and a signed-in student's schedule.
- What you can do
- Look up Wentworth course catalog information and a student's own schedule through the hosted calendar service.
- The manifest lists no individual tools, so the exact operations are not documented here.
- The underlying app also serves a read-only course catalog over REST and GraphQL without authentication.
- When to use it
- Useful for WIT students who want an assistant to check courses, catalog details, or their own class schedule without opening the school's calendar site.
- Requirements
- A remote endpoint at calendar.witcc.dev over streamable HTTP; OAuth sign-in with a WIT account is required. No environment variables or headers are declared.
Installation
In SourceWeft
- Open WIT Calendar 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/dev.witcc%2Fcalendar/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": {
"wit-calendar": {
"type": "http",
"url": "https://calendar.witcc.dev/api/mcp"
}
}
}README
Getting Started
You can set up the app on your own machine with mise, or in GitHub Codespaces.
Local Setup (mise)
mise installs Ruby, Node, Postgres, and the system libraries that the gems need. It also runs the project tasks. You need mise 2026.9.0 or later.
-
Clone the repository and go into it.
-
Trust the project config:
-
Get the development credentials key. See step 7 in Codespaces Setup.
-
Install everything and prepare the database:
This installs the system packages from
mise.toml, installs the tools, and then runsmise run setup. Postgres must be running before the setup step. -
Start the app:
Run mise tasks to see all tasks. Common tasks:
Put personal overrides in mise.local.toml. Git ignores that file.
Codespaces Setup
-
Create a new branch OR fork this repository
If you create a new branch, make sure it is named properly.
-
Click the green "Code" button towards the right of the screen
-
Click the "Codespaces" tab at the top of the pop-up
-
Click "Create codespace on
your-branch-name" -
Install dependencies:
Run in a new terminal window:
-
Set up Codespace:
Run the following command in the terminal:
-
Set up Rails credentials:
This project uses Rails encrypted credentials for storing sensitive configuration like Google OAuth credentials and Active Record encryption keys.
- Uses
config/credentials/development.yml.enc - Email @jasper [[email protected]] for the development key to decrypt the credentials.
-
Paste the key into
config/credentials/development.keyNote: You'll need to create the
development.keyfile. Ensure it is created in the correct directory (config/credentials).
-
- Uses
-
Set up the database:
-
Set up Google OAuth:
You will need to provide @jasper [[email protected]] your Codespace URL to be added to the development project on Google Cloud.
a. In the bottom panel of your Codespace, click the Ports tab as shown below: [image]
b. Right click port 3000 and set the port visibility to "Public" as shown below: [image]
c. Right click the "Forwarded Address" for port 3000 and click "Copy Local Address" as shown below: [image]
-
Run the application:
This will start the web server, the background job worker, and the CSS watcher. You can access the application at
http://127.0.0.1:3000/users/sign_inoryour-codespace-URL/users/sign_in(see the previous step for instructions for getting your Codespace URL).Note: If you click the "Open in Browser" on the notification that comes up within the Codespace after starting the server, you will be redirected to the root page of the server, which doesn't exist. You must manually append
/users/sign_into the end of the URL.
Public Catalog API
The app serves a read-only course catalog over REST and GraphQL. No authentication is needed. See docs/public-catalog-api.md.
Troubleshooting
If you run into any errors in the terminal you don't recogize, feel free to run them by @jasper [[email protected]].
Source: README.md at commit 34c3b86
Tools
0Version history
1- v1.0.0LatestNov 8, 2026
Score
75% 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
Declare a license in the repository or the registry entry.