Northeastern University Calendar MCP Server

Created By
jibinb961a year ago
Overview

What is the Northeastern University Calendar MCP Server?

The Northeastern University Calendar MCP Server provides access to the university's event calendar through the Model Context Protocol (MCP), allowing users to fetch, search, and filter events.

How to use the Northeastern University Calendar MCP Server?

To use the server, clone the repository, set up a virtual environment, install dependencies, and run the server. Connect it with the Claude Desktop app to interact with the calendar.

Key features of the Northeastern University Calendar MCP Server?

  • Fetch today's events
  • Retrieve upcoming events for a specified number of days
  • Search events by keywords
  • Filter events by category
  • Get detailed information about specific events
  • List available event categories

Use cases of the Northeastern University Calendar MCP Server?

  1. Finding out what events are happening today at Northeastern University.
  2. Checking upcoming workshops or athletic events.
  3. Searching for events by specific categories.

FAQ from the Northeastern University Calendar MCP Server?

  • How do I connect the MCP server to Claude Desktop?

Follow the setup instructions in the CLAUDE_DESKTOP_SETUP.md file after starting the server.

  • What should I do if Claude can't connect to the server?

Ensure the server is running and that port 8000 is not blocked by a firewall.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jibinb961
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago