Cookie expired and you already have a token? You don't need a new one and you don't need to touch your MCP client's config — just skip to the form below, enter your existing token and a fresh cookie, and submit. The token is what your MCP client is connected to; only the cookie(s) behind it change.
Tokens aren't tied to your name or account here — it's just a random key that maps to your connected session(s). If you lose it, generate a new one; there's no recovery, but you'll need to update your MCP client's config with the new one.
Save this now — it will not be shown again. Put it straight into your MCP client's config, or a password manager. Don't paste it anywhere else.
POLITEMall, NYP's own Brightspace, and STEP are three separate logins with separate cookies, even though they share the same SSO — connect whichever you need (any combination is fine, tools merge results automatically). All three only work from the polytechnic corporate network/VPN, so this has to happen in your own regular browser, not on this page.
F12) → Network tab, then reload the page.Cookie header (the whole string, e.g. d2lSessionVal=...; d2lSecureSessionVal=...).Treat all of these like passwords — don't paste them anywhere else. This page sends them directly and only to this server over HTTPS.