ohio-state

This MCP server exposes a broad set of OSU content APIs through a single interface, enabling language models to query athletics, buildings, transportation, academics, dining, library services, events, and more. The server compiles 50+ tools across 14 service categories, such as get_athletics_all to fetch athletics programs and schedules, get_buildings and get_building_details for campus facilities, get_bus_routes and get_bus_stops for transit data, and get_dining_locations or get_library_rooms for campus services. To use it, you run the Node.js server (or deploy via build artifacts) and point your MCP client at the provided endpoint. The example in the README shows how to wire the server into Claude Desktop or run it standalone with npm start, after which you can invoke any of the available tools by name with the appropriate parameters. The tools are designed to be composable for chat-based or agent-based workflows, enabling search, filtering, and retrieval across OSU’s campus systems.

Prerequisites:

• Node.js and npm installed on your machine
• Access to the repository containing the Ohio State MCP server or a published npm package

Install and build flow:

1. Clone the repository:

git clone https://github.com/your-organization/sichengchen-ohio-state-mcp-server.git
cd sichengchen-ohio-state-mcp-server

2. Install dependencies:

npm install

3. Build the server (produces build/index.js):

npm run build

4. Run the server:

npm start

If you are actively developing, you can use:

npm run dev

This enables automatic rebuilding on file changes.

Notes:

• Ensure any required API keys or access tokens for OSU APIs are configured in environment variables or a config file as documented by the project.
• The server is intended to be started in an environment where node is available; you can also containerize it with Docker if desired.

Tips and troubleshooting:

• If you see port or connection errors, verify that the server is running and that the host/port your MCP client uses matches the server output.
• The npm start script expects a built artifact at build/index.js; if you see missing file errors, run npm run build first.
• Environment variables for OSU APIs (if required by the backend) should be documented in a .env file or your deployment environment. Typical variables might include OSU_API_KEY, OSU_API_BASE_URL, or similar tokens.
• If you plan to use Claude Desktop or another MCP client, update the client configuration to point to the path to build/index.js (as shown in the README example) or adapt the endpoint accordingly for your deployment.
• The server exposes a large API surface; explore the available methods by inspecting the built API surface or consulting the repository docs to understand parameter expectations for each tool (e.g., search filters for buildings, date ranges for events).