EKKE University Assistant MCP

A read-only Model Context Protocol server for finding answers in EKKE course repositories, GitHub Discussions, and official university pages. It returns source links and dates where available. No model or backend is included: the MCP client supplies the model.

Magyarul és angolul is lehet keresni. The search expands common Hungarian and English academic terms in both directions (for example, vizsgaidőszak ↔ exam period, tárgybővítés ↔ course add). Results stay in the language they were published in, so the MCP client can answer in the user's language while citing the original source.

Tools

• search_course_content(query, language?, limit?) searches Markdown/text course materials, public issues, and GitHub Discussions from the configured repositories.

• search_official_ekke(query, language?, limit?) searches indexed pages from official EKKE domains and includes curated links for the academic calendar, course descriptions, the Study Office, and scholarships.

The language option (auto, hu, en, both) controls response labels; it never restricts search to one language. Query expansion is rule-based and deliberately small, not machine translation.

Related MCP server: ContractAudit MCP Server

npm package

The package is named ekke-mcp. After release, it can be installed with:

npx ekke-mcp

For local development and packing:

pnpm install
pnpm build
pnpm test
pnpm pack

Versioning and releases

Choose the version bump that matches the change. Each script creates a conventional release commit and an annotated vX.Y.Z Git tag:

pnpm release:patch # bugfix
pnpm release:minor # backward-compatible feature
pnpm release:major # breaking change
git push origin main --follow-tags

These run pnpm version patch|minor|major --message "chore: release v%s". The working tree must be clean. Note that pnpm patch by itself patches a dependency; pnpm version is the package version bump.

Pushing the tag starts the release workflow. It reruns the build and tests, publishes ekke-mcp to npm using npm trusted publishing, publishes the scoped @ekke-edu/ekke-mcp package to GitHub Packages, and creates a GitHub Release with generated notes and the .tgz attached. GitHub Packages requires a scoped package name, so its install name differs from the unscoped npm package. The workflow skips registry versions that already exist and can safely finish an interrupted release.

To finish a release that is already on npm but missing from GitHub Packages, open Actions → Release → Run workflow, choose main, and enter the tag (for example, v0.2.2). This republishes only to registries where that version is missing and attaches the package archive to the existing GitHub Release.

Before the first automated release, configure npm trusted publishing for ekke-mcp on npmjs.com: select GitHub Actions, organization ekke-edu, repository mcp, and workflow filename release.yml; allow direct publishing. This uses OIDC and needs no npm token secret. The workflow links the GitHub Packages copy to this repository through the repository field. GitHub makes the package private on first publish by default; confirm its visibility in the package settings after the first release, since the organization may disable inherited repository permissions.

Install from GitHub Packages with @ekke-edu:registry=https://npm.pkg.github.com configured in .npmrc, then run npm install @ekke-edu/ekke-mcp.

Requirements

• Node.js 22+ and pnpm 11.25.0 for development

• A GitHub token with read-only access to the public EKKE repositories. GitHub's Discussions GraphQL API requires authentication. For a classic token, GitHub documents public_repo scope for public repositories; a fine-grained token can be limited to the required repositories and read-only permissions.

• Network access to GitHub and the official EKKE domains.

Without GITHUB_TOKEN, course files and issues can still be searched (subject to GitHub's unauthenticated API rate limit), but Discussions are skipped. The official-site search does not require a token.

Run locally

Set GITHUB_TOKEN in the environment running the MCP client. For PowerShell:

$env:GITHUB_TOKEN = "YOUR_READ_ONLY_TOKEN"
pnpm dev

After building, run pnpm start. A host can also launch the npm binary as a stdio MCP server and pass GITHUB_TOKEN in its environment:

{
  "mcpServers": {
    "ekke-university-assistant": {
      "command": "npx",
      "args": ["-y", "ekke-mcp"],
      "env": {
        "GITHUB_TOKEN": "${input:ekkeGitHubToken}"
      }
    }
  }
}

Do not commit a real token. See .env.example for the supported environment variables.

Configuration

Non-secret defaults are stored in config/sources.json. You can edit repository lists, official host allowlists, sitemaps, and curated links there. Environment variables override repository lists:

• EKKE_COURSE_REPOS: comma-separated public repositories containing course materials.

• EKKE_DISCUSSION_REPOS: comma-separated repositories whose Discussions should be searched.

Search results are cached in memory for 15 minutes. Official-site discovery uses sitemaps when available and only fetches HTTPS pages hosted under configured EKKE domains.

No student records or Neptun credentials are accessed. This first version is read-only and has no hosted chat or model API key.