Zohairs Server

MCP开发工具

提供方 Zohair-coder

开发工具 未标注 API Key 社区 / 第三方

Test

一句话选型结论

按资料字段整理

Zohairs Server 属于开发工具类 MCP 服务器,传输方式未标注,API Key,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 基础信息齐全,可以先按官方文档接入试跑。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zohairs Server当前 未标注 未标注 未标注 无 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Zohair-coder上游标注的维护方 Zohair-coder
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

11.1 KB
来自项目仓库与上游目录的原文,未做删改

UI for data: https://scheduler.zohair.dev

TMS-Scraper

Scrapes data from the Drexel Term Master Schedule and outputs a JSON file. Note that this scraper is not officially supported by Drexel University, and may break if the term master schedule website changes.

Installation

Make sure git is installed. Clone the repository:```bash
git clone https://github.com/Zohair-coder/drexel-scraper.git
cd drexel-scraper


Make sure you have Python 3 installed. Then install the dependencies by running the following command:

###### Mac/Linux```bash
pip3 install -r requirements.txt
playwright install
Windows```bash

pip install -r requirements.txt
playwright install


## Usage

First, set up authentication.
Then, to run the scraper, simply run:

###### Mac/Linux```bash
python3 src/main.py
Windows```bash

python src/main.py


The scraper will output a JSON file called `data.json` in the same directory as the scraper.

#### Automatic Quarter Detection

The scraper now automatically detects the current Drexel quarter based on the current date. You no longer need to manually update the `year` and `quarter` values in `src/config.py`. The system uses the following schedule:

- **Fall Quarter (15)**: July 1 - September 27
- **Winter Quarter (25)**: September 28 - January 15
- **Spring Quarter (35)**: January 16 - April 14
- **Summer Quarter (45)**: April 15 - June 30

If you need to override the automatic detection (e.g., for testing or scraping a specific past/future quarter), you can set the `DREXEL_YEAR` and `DREXEL_QUARTER` environment variables:```bash
export DREXEL_YEAR=2024
export DREXEL_QUARTER=35  # Spring quarter

You can still modify the college_code variable in src/config.py to scrape a specific college.

To view all the options that the scraper supports, run python3 src/main.py --help on Mac/Linux, or python src/main.py --help on Windows.

Authentication

Since the term master schedule is only accessible to logged-in Drexel students, to run the scraper, you will need to provide your Drexel credentials as well as provide multi-factor authentication (MFA).

To provide your Drexel credentials, set the environment variable DREXEL_EMAIL to your Drexel email (abc123@drexel.edu) and DREXEL_PASSWORD to the password you use to login to Drexel One. You can follow this guide for Windows, and this guide for MacOS to set environment variables.

You will also need to go to this page and make sure "Authenticator app or hardware token" is the preferred sign-in method. Unfortunately, if you use Microsoft Authenticator as your MFA app you will not be able to run the scraper. You will have to delete the Microsoft Authenticator sign in method and install a different MFA app.

There are two ways to provide MFA for the script to authenticate with. The first is easier if you're looking to run the script manually and quickly. The second is better if you are going to be running the script frequently, or if it needs to be automated.

Authenticate manually

You will authenticate the scraper manually as if you were logging into Drexel One, using a one-time code either from an authenticator app or that is texted to you. After setting the DREXEL_EMAIL and DREXEL_PASSWORD environment variables, run the scraper as explained above, and you will be prompted for your verification code.

Authenticate using a secret key

If you set this up, you will not need to manually enter an authentication code each time you run the scraper.

  1. Go to connect.drexel.edu.
  2. Click 'Help & Settings', then 'Change MFA settings'.
  3. Log in to the Microsoft portal, then click 'Add sign-in method' on the 'Security info' tab.
  4. Select 'Authenticator app' for the method, and click 'Add'.
  5. Select 'I want to use a different authenticator app', and then 'Next'.
  6. Select 'Can't scan image?' when prompted with a QR code, and you should see an Account name and Secret key.
  7. Set your DREXEL_MFA_SECRET_KEY environment variable to the given Secret key.
  8. Select 'Next', you should be prompted to enter an authentication code.
  9. With the secret key environment variable set, run python3 src/totp.py which will generate a one-time code.
  10. Enter this code into the Microsoft website, and select 'Next'
  11. 'Authenticator app' with TOTP should have been added to the list of available methods.

Now, when you run the scraper as explained above, it should authenticate itself automatically using this secret key.

All Colleges

To scrape all colleges instead of just the one specified in the src/config.py, run the following command:

Mac/Linux```bash

python3 src/main.py --all-colleges


###### Windows```bash
python src/main.py --all-colleges

Multiple quarters

Grafana's Quarter selector lists quarters currently advertised by TMS. To
collect every available quarter and college, including course details and ratings:```bash
python3 src/main.py --db --all-quarters --all-colleges --ratings


Use `--term 202625` to refresh only Winter Quarter 26-27. Without either quarter flag,
the existing configured/automatic quarter selection applies. Each quarter is
stored independently; a failed refresh retains its previous data. The scheduled
container collects all quarters. See the architecture and migration notes.

#### Ratings

To also include the ratings field in `data.json` that requests data from RateMyProfessor, run the following command:

###### Mac/Linux```bash
python3 src/main.py --ratings
Windows```bash

python src/main.py --ratings


Note that this will take longer to run since the scraper has to look up the rating on RateMyProfessors. However, it will cache the ratings in a file called `ratings_cache.json` (inside the `cache` directory) so that it doesn't have to look up the same professor again, which will run much faster. If you want to clear the cache to get new ratings, simply delete the `ratings_cache.json` file.

#### PostgreSQL

To add the data to a PostgreSQL database, make sure the PostgreSQL server is installed and running in the background. Check the settings in the db_config.py file. It is recommended that you set the necessary environment variables listed in the file, but if not, it will use the defaults for Postgres. You can follow this guide for Windows, and this guide for MacOS to set environment variables.

Then run the scraper with the `--db` flag:

###### Mac/Linux```bash
python3 src/main.py --db
Windows```bash

python src/main.py --db


This creates the database/tables if needed and atomically replaces only the
selected quarter's data. Existing single-quarter databases are migrated while
preserving their old tables in `legacy_single_quarter`. To initialize or migrate
without scraping, use:```bash
python3 src/main.py --migrate-only

To view the schema for the tables, you can look at the src/create_tables.sql file.

Connect to the database using the following command:```bash
psql -U postgres schedulerdb
``````sql
schedulerdb=# SELECT * FROM courses;
schedulerdb=# SELECT * FROM instructors;
schedulerdb=# SELECT * FROM terms;
schedulerdb=# SELECT * FROM course_instructors;
schedulerdb=# SELECT * FROM all_course_instructor_data;


I recommend viewing the data using another program like pgAdmin.

You can also combine all the options together:

###### Mac/Linux```bash
python3 src/main.py --db --all-colleges --ratings
Windows```bash

python src/main.py --db --all-colleges --ratings


## Docker

You can also run the scraper in a Docker container. Make sure Docker is installed. You can then either open up the folder in VS Code as a Dev Container (preferred), or run the following command to run it:```bash
docker compose up -d --build

Make sure you execute this in the project root directory. Let the scraper container finish/exit. The scraper should then output the data.json file in the same directory. You can view the data inside the database by going to http://localhost:30012 in your browser.

You can also view an editable Grafana instance at http://localhost:3000. Docker Compose automatically provisions the PostgreSQL data source and the same Scheduler Dashboard that is deployed to dev and production. Anonymous access has the Admin role locally, so no login or manual import is required. To edit the dashboard, use its canonical URL: http://localhost:3000/d/db64b0ee-89cf-46ab-a3f5-af315d8e1e0f/scheduler-dashboard. Grafana treats the dashboard shown at / as its special home dashboard and only offers Save as copy there.

The local dashboard starts from k8s/drexel-scraper/dashboards/scheduler.json. After making changes, click Save dashboard. Grafana recognizes that the dashboard came from a provisioning file and displays a Provisioned dashboard dialog instead of saving it to its database. Click Copy JSON to clipboard, then promote the clipboard contents back to the canonical dashboard file on macOS with:```bash
./scripts/promote-local-dashboard.sh --clipboard


Alternatively, click **Save JSON to file** and pass the downloaded file to the script:```bash
./scripts/promote-local-dashboard.sh ~/Downloads/scheduler.json

The script also accepts - for standard input. It removes Grafana's database-specific ID, resets the dashboard version, and validates the dashboard UID, PostgreSQL data-source UID, and production-only PostHog guard before replacing the canonical file. Review the resulting Git diff and commit it normally. A push to dev deploys the dashboard to dev; merging to main deploys the same dashboard to production. The deployed dashboards are read-only.

The PostHog script is included in the shared dashboard but only initializes on scheduler.zohair.dev or www.scheduler.zohair.dev, so local and dev activity is not tracked by the production PostHog project.

To run the script again after the container has exited, run the following command:```bash
docker compose up -d


To delete the containers, run the following command:```bash
docker compose down

If you want to reset the database, delete the postgres-data directory inside the project root directory.

If you want to reset the local Grafana database and discard unpromoted UI changes, delete the grafana_data directory inside the project root directory. The next startup provisions a fresh copy of the committed dashboard.

NOTE: Docker Compose is only used for local development. The production version of the scraper uses Kubernetes. The Kubernetes configuration files live in the k8s directory.

Contributing

If you wish to contribute, please take a look at the "Issues" tab and see if there are any issues you can help with. If you wish to add/request a new feature, you can create a new issue, and we can talk about it there before you start working on it. If you wish to work on an existing issue, please comment on the issue so that I can assign it to you. Once you have completed the issue, you can create a pull request to the dev branch, and I will review it. After merging the changes to the dev branch, the job will be deployed on the dev server (https://schedulerdev.zohair.dev). If there are no issues, I will merge the changes to the main branch, and the job will be deployed on the main server (https://scheduler.zohair.dev).

If you want to contact me directly, you can email me at zohair.ul.hasan@gmail.com.

常见问题

5 问
答案由本站依据条目字段整理,不引用上游原文
Zohairs Server 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Zohairs Server 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Zohairs Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zohairs Server 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Zohairs Server 能提供哪些能力?

资料显示能力标签包括 API密钥、开发工具、命令行工具。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。