infinitecampus-api

Infinite Campus via curl (no MCP)

Infinite Campus's Campus Parent portal is a classic server-rendered site (no public API, no bot wall). A plain form POST to verify.jsp logs a parent in and hands back a session cookie — no browser bridge needed. This is the same login infinitecampus-mcp's src/client.ts/src/auth.ts do; this skill reproduces it with curl + a cookie jar.

Infinite Campus is per-district. Every parent's portal lives at their own district's host (https://campus.<district>.k12.example.us or similar) under an appName path segment. There is no shared IC endpoint — carry the base URL and district from the same config the MCP uses:

: "${IC_BASE_URL:?set to your district's portal URL, e.g. https://campus.yourdistrict.org}"
: "${IC_DISTRICT:?set to the appName path segment, e.g. yourdistrict}"
: "${IC_USERNAME:?parent portal username}"
: "${IC_PASSWORD:?parent portal password}"

(Same 4 env vars the MCP reads — reuse the repo's .env or the host's secret store; don't hardcode a district.)

One-time setup

None — curl and jq are the only tools needed (brew install jq if missing). No profile/pairing step, no extension.

Login (capture cookies + XSRF token)

verify.jsp accepts a urlencoded form POST and returns 200 with an <AUTHENTICATION>state</AUTHENTICATION> marker in the body — not via HTTP status — plus ~20 Set-Cookie headers. Use a cookie jar so curl does the Set-Cookie parsing/deduping for you:

JAR=$(mktemp)
BODY=$(curl -sS -c "$JAR" \
  "$IC_BASE_URL/campus/verify.jsp?nonBrowser=true" \
  --data-urlencode "username=$IC_USERNAME" \
  --data-urlencode "password=$IC_PASSWORD" \
  --data-urlencode "appName=$IC_DISTRICT" \
  --data-urlencode "portalLoginPage=parents")

echo "$BODY" | grep -o '<AUTHENTICATION>[^<]*' # AUTHENTICATIONsuccess = good

password-error / account-locked / any non-success state means the login failed — check that string before doing anything else. Credentials go in the form body (never the query string — it lands in access logs).