RaivatEdu Education MCP Server

An unofficial, read-only Model Context Protocol (MCP) server that lets Claude Desktop (or any MCP client) explore the public RaivatEdu website — raivatedu.com — using natural language.

RaivatEdu is admissions & student-relationship software (a SaaS marketing site), not a course catalog. This server reflects what the site actually publishes: product/feature information, pricing by market, solutions by audience, resource articles, and contact details. It fetches only public marketing pages, honours robots.txt, and never touches private/authenticated areas.

Table of contents

• Verified website capability analysis

• What this server exposes

• Architecture

• Prerequisites

• Installation, build & run

• Claude Desktop integration

• MCP tool reference

• Resources & prompts

• Environment variables

• Testing

• Example conversations

• End-to-end verification checklist

• Security considerations

• Known limitations

• Troubleshooting

• License

Related MCP server: HitKeep

Verified website capability analysis

Inspected live on 2026-10-13 via robots.txt, /sitemap.xml (+ its three child sitemaps), raw HTML, and embedded JSON-LD.

Capability → tool mapping

What this server exposes

10 tools, 4 resources (2 of them templated per market), and 4 prompts — all read-only.

Architecture

raivat-education-mcp/
├── src/
│   ├── index.ts                 # Entry point: stdio transport, CLI flags, graceful shutdown
│   ├── server.ts                # Builds McpServer + context; wires tools/resources/prompts
│   ├── config.ts                # Env config + the verified page/market/feature catalog
│   ├── context.ts               # ServerContext (config + client + logger)
│   ├── tools/
│   │   ├── index.ts             # registerAllTools
│   │   ├── shared.ts            # response formatting, shared Zod fields, char limit
│   │   ├── website.ts           # check_website_status, get_website_info, get_contact_information
│   │   ├── pages.ts             # list_pages, get_page_content, search_content
│   │   ├── pricing.ts           # get_pricing
│   │   └── catalog.ts           # list_features, list_solutions, list_resources
│   ├── services/
│   │   ├── website-client.ts    # SSRF-safe fetch: timeouts, retries, rate limiting
│   │   └── content-parser.ts    # Cheerio + JSON-LD extraction (pricing/org/software/FAQ)
│   ├── resources/index.ts       # raivatedu://info | contact | pages/{market} | pricing/{market}
│   ├── prompts/index.ts         # find_relevant_plan, compare_plans, summarize_page, navigate_website
│   └── utils/
│       ├── url.ts               # SSRF guard + catalog generation + path normalization
│       ├── errors.ts            # Typed errors + MCP error-result builder
│       └── logger.ts            # Leveled stderr-only logger
├── tests/                       # Vitest unit + integration tests (+ optional live smoke)
├── .env.example
├── claude_desktop_config.example.json
├── eval/evaluation.xml          # MCP evaluation questions
├── package.json / tsconfig.json / vitest.config.ts
├── README.md / LICENSE

Design highlights

• stdio transport, logs on stderr only (stdout stays a clean JSON-RPC stream).

• Structured output: every tool returns both human-readable text and structuredContent (toggle with response_format: "json").

• JSON-LD first: pricing/org/contact come from the site's own machine-readable schema.org data, not brittle CSS selectors.

• SSRF-hardened: outbound requests are restricted to raivatedu.com/www.raivatedu.com over HTTPS and to the sitemap-derived page allowlist; /api/ is always blocked.

• Polite client: per-request timeout, bounded retries with backoff, and a minimum interval between requests.

Prerequisites

• Node.js ≥ 18 (fetch is built in; developed/tested on Node 22+). Download Node.js.

• npm (bundled with Node).

• Claude Desktop (latest) for the integration section — download.

Installation, build & run

# 1. Get the project (clone your fork, or copy this folder)
cd raivat-education-mcp

# 2. Install dependencies
npm install

# 3. Build TypeScript -> dist/
npm run build

# 4. (optional) configure — all vars are optional
cp .env.example .env

# 5. Run the server (stdio). It waits for an MCP client on stdin/stdout.
npm start
# or directly:
node dist/index.js

Quick sanity checks (do not speak MCP, just prove the binary works):

node dist/index.js --version   # -> 1.0.0
node dist/index.js --help

Development with auto-reload:

npm run dev

Claude Desktop integration

1. Install Node.js (see prerequisites) and note the absolute path to node:

   • macOS/Linux: which node

   • Windows (PowerShell): (Get-Command node).Source

2. Build the project (npm run build) so dist/index.js exists.

3. Find the absolute path to the built entry file:

   • macOS/Linux: realpath dist/index.js

   • Windows (PowerShell): (Resolve-Path dist\index.js).Path

4. Edit Claude Desktop's config file (claude_desktop_config.json):

   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

   • Windows: %APPDATA%\Claude\claude_desktop_config.json

   • You can open it from Claude Desktop → Settings → Developer → Edit Config.

5. Add this server under mcpServers (see claude_desktop_config.example.json). Replace the example path with your own absolute path. On Windows, use double backslashes (\\).

   {
     "mcpServers": {
       "raivat-education": {
         "command": "node",
         "args": ["/ABSOLUTE/PATH/TO/raivat-education-mcp/dist/index.js"],
         "env": {
           "RAIVATEDU_DEFAULT_MARKET": "in"
         }
       }
     }
   }

   Windows example args: ["C:\\Users\\you\\Desktop\\Raivat_MCP\\dist\\index.js"]

6. Fully quit and reopen Claude Desktop (not just close the window).

7. Verify: open a new chat → click the tools/plug icon → you should see raivat-education with 10 tools. Ask: "Is the RaivatEdu website up?"

Tip: prefer node + absolute dist/index.js over npx/tsx for reliability. Ensure node is on the PATH Claude Desktop sees, or use an absolute path to the node binary in command.

MCP tool reference

All tools are read-only (readOnlyHint: true) and accept an optional response_format of "markdown" (default) or "json". Markets: in, us, gb, ca, au, nz, ie, sg, ae, za (default in, configurable).

raivatedu_check_website_status

Check reachability and response time (HTTP HEAD to a market home page).

• Input: market?, response_format?

• Output: { reachable, status, url, response_time_ms, checked_at }

• Example: { "market": "in" } → ✅ reachable, HTTP 200, 180 ms

raivatedu_get_website_info

Product, organization and markets overview from JSON-LD.

• Input: market?, response_format?

• Output: { product{...}, organization{...}, markets[], source_url }

raivatedu_get_contact_information

Published contact emails + contact/demo page URLs (does not send anything).

• Input: market?, response_format?

• Output: { general_email, contact_points[], contact_page, demo_page }

raivatedu_get_pricing

Subscription plans & prices for a market, from pricing JSON-LD offers.

• Input: market?, response_format?

• Output: { market, currency, plans:[{ plan, billing, price, currency, unit, minUsers?, maxUsers?, url? }], source_url }

• Example (in): Starter 3500 INR, Professional 4500 INR, Enterprise 8000 INR, per user/month.

raivatedu_list_features

The 9 feature areas with URLs (optional live descriptions).

• Input: market?, include_descriptions? (default false), response_format?

• Output: { market, count, features:[{ slug, label, url, description? }] }

raivatedu_list_solutions

The 4 audience segments (Schools, Colleges & Universities, Coaching Institutes, Training & EdTech).

• Input: market?, include_descriptions?, response_format?

• Output: { market, count, solutions:[{ slug, label, url, description? }] }

raivatedu_list_resources

Resource articles + resources/blog/guides/help landing pages.

• Input: market?, include_descriptions?, response_format?

• Output: { market, landing_pages{...}, count, articles:[{ slug, label, url, description? }] }

raivatedu_list_pages

The site navigation map (verified page catalog) for a market.

• Input: market?, type? (e.g. "feature", "solution", "resource-article"), response_format?

• Output: { market, count, pages:[{ path, url, type, market }] }

raivatedu_get_page_content

Fetch & summarize a specific public page (title, description, outline, body text, links, FAQ).

• Input: path (required, path or full raivatedu.com URL), max_text_chars? (200–20000, default 6000), include_links? (default true), response_format?

• Output: { url, type, title, description, canonical, headings[], text, faqs[], links[] }

• Errors: unknown path → "not a known public RaivatEdu page"; external host → refused (SSRF); /api/* → blocked.

raivatedu_search_content

Keyword search across ~28 content-rich pages for a market; ranked results with snippets.

• Input: query (required, 2–200 chars), market?, limit? (1–20, default 5), response_format?

• Output: { query, market, pages_searched, count, results:[{ title, url, type, score, snippet }] }

• Empty matches return count: 0 (not an error).

Resources & prompts

Resources (read-only, JSON):

• raivatedu://info — product/org/markets overview

• raivatedu://contact — contact details

• raivatedu://pages/{market} — page catalog (templated; lists all 10 markets)

• raivatedu://pricing/{market} — pricing plans (templated; lists all 10 markets)

Prompts:

• find_relevant_plan — args institution_type, team_size?, market?

• compare_plans — arg market?

• summarize_page — arg path

• navigate_website — args goal, market?

Environment variables

All optional; the server runs with zero config. See .env.example.

Testing

npm test          # offline unit + integration tests (mocked HTTP) — 51 tests
npm run typecheck # tsc --noEmit
RUN_SMOKE=1 npm test   # also runs optional live tests against raivatedu.com

Coverage includes: config parsing, SSRF/path validation & catalog, HTML/JSON-LD parsing, the HTTP client (success, 404, 5xx retries, network errors, timeouts, host blocking), tool discovery, every tool's happy path, input validation, unknown-path & SSRF rejection, empty search results, and malformed-HTML/JSON-LD handling.

MCP Inspector

npm run build
npx @modelcontextprotocol/inspector node dist/index.js
# or:  npm run inspector

The Inspector opens a UI where you can list/call tools, read resources, and try prompts interactively.

Example conversations

Once connected in Claude Desktop you can ask:

• "Is the RaivatEdu website up right now?" → raivatedu_check_website_status

• "What is RaivatEdu and who makes it?" → raivatedu_get_website_info

• "How much does RaivatEdu cost in India? Compare the plans." → raivatedu_get_pricing (try the compare_plans prompt)

• "I run a coaching institute with ~15 counsellors — which plan and solution fits?" → find_relevant_plan → raivatedu_get_pricing + raivatedu_list_solutions

• "Where does the site talk about WhatsApp follow-ups?" → raivatedu_search_content

• "Summarize the Admissions feature page." → summarize_page → raivatedu_get_page_content

• "List all the resource articles and give me the one about migrating from spreadsheets." → raivatedu_list_resources + raivatedu_get_page_content

• "What are RaivatEdu's sales and support email addresses?" → raivatedu_get_contact_information

• "Show me the US pricing resource." → read resource raivatedu://pricing/us

End-to-end verification checklist

• npm install completes.

• npm run build succeeds; dist/index.js exists.

• node dist/index.js --version prints 1.0.0.

• npm test → all offline tests pass.

• RUN_SMOKE=1 npm test → live tests pass (site reachable, INR pricing present).

• npx @modelcontextprotocol/inspector node dist/index.js lists 10 tools, 4 prompts, resources.

• In Inspector, raivatedu_get_pricing {market:"in"} returns 3 INR plans.

• In Inspector, raivatedu_get_page_content {path:"https://evil.example.com"} is refused.

• Claude Desktop config added with the correct absolute path; app fully restarted.

• Tools icon shows raivat-education with 10 tools.

• "Is the RaivatEdu website up?" triggers raivatedu_check_website_status and answers.

Security considerations

• Read-only. No tool writes, submits forms, sends messages, or authenticates. Contact tools only surface already-public email addresses.

• SSRF prevention. Outbound fetches are restricted to raivatedu.com/www.raivatedu.com over HTTP(S), and only to paths in the verified sitemap-derived allowlist. Full URLs are parsed and host-checked; redirects are re-validated against the allowlist. Arbitrary/internal/external URLs are refused.

• robots.txt respected. /api/ is always blocked, matching the site's Disallow: /api/.

• No access-control bypass. The server never attempts auth, CAPTCHAs, paywalls, or private areas.

• Untrusted content. Page text is treated as data, not instructions (stated in the server instructions and the summarize_page prompt). Returned text is inert; nothing is executed.

• No secrets. No credentials, cookies, or tokens are used, stored, or logged. Logs go to stderr and contain only URLs/status/timing.

• Polite. Timeouts, bounded retries with backoff, and a configurable minimum request interval protect the origin.

• Input validation. All inputs validated with Zod (.strict() where applicable) with length/range constraints.

Known limitations

• Not a course catalog. RaivatEdu publishes no public courses, categories, user accounts, or search API, so there are intentionally no list_courses/get_course_details/list_categories tools. Course-like names on the site are sample data only.

• search_content is client-side over ~28 curated pages per market — it is not a full-site crawl or a live search index.

• Scope = public marketing pages. The authenticated product (app.raivatedu.com) and /api/ are out of scope by design.

• Catalog is a snapshot. Page/feature/market lists were captured on 2026-10-13. If the site adds pages, update src/config.ts (and the catalog count test). Tools degrade gracefully (404 → clear error) if a page is removed.

• include_descriptions: true issues one request per item (slower); off by default.

Troubleshooting

Use as a plugin

This repo ships an Open Plugins component at .mcp.json, so any MCP client that reads plugin repos can pick the server up directly. It points at the hosted, read-only endpoint:

{
  "mcpServers": {
    "raivat-education": {
      "type": "http",
      "url": "https://mcp.raivatedu.com/mcp"
    }
  }
}

No API key is required — the server holds no customer data and performs no write actions. To run it yourself instead, see the stdio and HTTP instructions above.

License

MIT — see LICENSE. Independent/unofficial; "RaivatEdu" marks belong to RaivatEdu Technologies Pvt. Ltd. Not affiliated or endorsed.