Fuxam Student MCP
Connect your CODE University Fuxam account to an AI agent through one hosted MCP.
Fuxam Student MCP lets Codex, Claude, and other compatible agents explore your modules, learning units, progress, schedule, and semester options through one hosted service.
Let your agent connect it
Copy this prompt into a new chat with Codex or Claude:
Connect Fuxam Student MCP for me using this documentation:
https://codecampus.tools/docs/fuxam-student-mcp
Configure this hosted Streamable HTTP MCP server in my current client:
https://fuxam-mcp.codecampus.tools/mcp
Complete every step you can directly. When the browser authorization page opens, pause and walk me through these exact actions: sign in at fuxam.app without opening Developer Tools there; open the linked clerk.fuxam.app client page; open Developer Tools on that Clerk page; reload the Clerk page; and copy the `client` network request as cURL. Never ask me to paste the request into chat, and never print or log it.
After authorization, verify that the MCP tools are available and run one read-only check: show the module categories and learning units I can currently choose from. Do not book or unbook courses, or join or leave waitlists, during setup.Connect
1. Add the hosted MCP
codex mcp add fuxam --url https://fuxam-mcp.codecampus.tools/mcp
codex mcp login fuxamThe second command opens browser authorization. Start a new task after it succeeds.
- Open Settings → MCP servers → Add server.
- Name it
fuxam, choose Streamable HTTP, and enterhttps://fuxam-mcp.codecampus.tools/mcp. - Save, restart when prompted, then select Authenticate for
fuxam.
The desktop app, Codex CLI, and Codex IDE extension share MCP configuration on the same Codex host.
claude mcp add --transport http --scope user fuxam https://fuxam-mcp.codecampus.tools/mcpOpen Claude Code, run /mcp, select fuxam, and complete authentication. User scope makes the connection available across your local projects.
- Open Customize → Connectors.
- Select + → Add custom connector.
- Name it
Fuxam Student MCP, enterhttps://fuxam-mcp.codecampus.tools/mcp, and add it without custom OAuth credentials. - Select Connect, complete authentication, and enable the connector for the conversation.
On Team or Enterprise plans, an Owner must first add the custom connector in Organization settings → Connectors. Remote connectors belong here, not in claude_desktop_config.json.
Your client opens the Fuxam Student MCP authorization page. Leave that page open and follow the next steps.
2. Sign in to Fuxam — do not inspect anything there
- Open fuxam.app in a separate tab and sign in.
- Once the dashboard loads, leave the tab alone. You only use it to establish your signed-in session.
Do not open Developer Tools onfuxam.appDo not inspect, copy, or paste any request from the Fuxam dashboard. Nothing from that tab is entered into the authorization form.
3. Open the exact Clerk page
-
While you remain signed in to Fuxam, open the Clerk client page in another tab.
-
Check the address bar. It must begin with:
https://clerk.fuxam.app/v1/client -
The page may display a large JSON response. That is expected—do not copy the JSON or use Copy response.
4. Open Developer Tools on the Clerk tab and copy one request
- Stay on the
clerk.fuxam.app/v1/clienttab. - Open browser Developer Tools and select Network.
- Reload the Clerk client page while the Network panel is open.
- Filter the Network list for
client. - Find the request whose URL begins with
https://clerk.fuxam.app/v1/client. - Right-click that network request and choose Copy as cURL. The submenu may be named Copy or Copy Value, depending on the browser.
- Return to the Fuxam Student MCP authorization page, paste the entire cURL command into the form, and select Connect.
Before connecting, confirm all three statements are true:
- The page where Developer Tools is open is
clerk.fuxam.app, notfuxam.app. - You copied the
clientrequest as cURL, not its response or JSON body. - You are pasting into the authorization page, not an AI chat.
Keep the copied request privateIt contains a cookie that gives access to your Fuxam session. Enter it only on the Fuxam Student MCP authorization page. Do not paste it into a chat, commit it, or include it in a screenshot.
The service extracts and stores only the exact __client cookie; other copied headers and cookies are discarded. You can also paste only the raw __client value if you already have it. You do not install a package or run a local server.
Authorization is fail-closed. The service creates a grant only after Fuxam confirms an active session for the supported CODE institution and exposes one usable study-program context. Missing, expired, malformed, unsupported, or otherwise unsuccessful authentication is rejected without an authorization code or grant.
Current client references: Codex MCP, Claude Code MCP, and Claude custom connectors.
5. Start with a read-only prompt
Show me the module categories and learning units I can currently choose from.
Try something useful
- “Help me compare these three modules, including requirements, progress, instructors, dates, and workload.”
- “Look at my study plan and current progress, then help me assemble a realistic semester.”
- “Check whether this proposed set of learning units has scheduling conflicts.”
- “What deadlines and appointments do I have over the next month?”
The agent can browse by category, tag, or text; inspect several modules and learning units together; compare them with your progress; and check a proposed course set for conflicts.
What it can do
Search by category, tag, or text. Compare options with descriptions, requirements, responsible people, dates, capacity, and course relationships.
Inspect your study plan, progress, attempts, requirements, and exam details.
Read appointments, deadlines, excluded dates, pinned courses, and todos. Check a proposed course set for conflicts.
Book or unbook a course and join or leave a waitlist through verified Fuxam changes.
Account changes are realBooking and waitlist actions affect your Fuxam account. The MCP marks them as write operations and verifies the resulting state after each change. It does not silently book courses or run an implicit conflict check.
Authentication
Each authorization is isolated to one student. The hosted service stores the Fuxam cookie and authenticated account context as encrypted authorization properties. It uses the cookie to renew Fuxam's short-lived session token when needed.
If the cookie expires, reconnect the MCP and complete authorization again with a newly copied Clerk client request.
Troubleshooting
I cannot find the client request
Sign in to fuxam.app, but do not open Developer Tools there. Open the linked Clerk client page in another tab, confirm its address begins with https://clerk.fuxam.app/v1/client, open Developer Tools → Network on that Clerk tab, and reload the Clerk page. Filter for client and use the request's Copy as cURL action—not Copy response and not the JSON shown on the page or in the response panel.
The copied request does not contain __client
You copied the response body or the wrong network request. Copy the complete client request as cURL after signing in to Fuxam. Paste it only into the MCP authorization page. The page accepts the full cURL command or the raw __client value; it does not accept the /v1/client JSON response.
Fuxam could not authenticate this connection
The copied session is missing, expired, or no longer active. Sign out of Fuxam, sign back into the intended account, open a newly loaded Clerk client page, and copy a fresh client request as cURL. Do not reuse an older copied request.
The OAuth callback failed or the authorization page expired
Start authentication again from the MCP client. OAuth URLs contain short-lived state, PKCE, and client-specific callback details and should not be bookmarked or reused. In Codex, run codex mcp login fuxam again. In Claude Code, open /mcp, select fuxam, and reconnect it. Keep the client running until the browser reports that authorization completed.
Authorization completed, but the tools are unavailable
Confirm that the configured server is https://fuxam-mcp.codecampus.tools/mcp, not a local command or the staging URL. Enable the MCP or connector for the conversation, then start a new chat or restart the client. In Codex, codex mcp list should show fuxam as enabled with OAuth. In Claude Code, /mcp should show fuxam as connected.
FUXAM_AUTH_REQUIRED
Your configured Fuxam session is missing or expired. Sign in again, reconnect the MCP, and paste a newly copied Clerk client request on the authorization page. You do not need to remove and re-add the server.
FUXAM_UNSUPPORTED_INSTITUTION
This service supports accounts whose Fuxam institution is CODE University.
FUXAM_CONTEXT_REQUIRED
The MCP could not identify exactly one usable study-program context for the authenticated account. Confirm that your CODE study program and cohort are visible in Fuxam. If they are, send the exact error code—not your cookie or copied request—to Max.
FUXAM_SESSION_CHANGED
The active Fuxam account changed while a request was running. Retry the tool call. If it happens again, reconnect the MCP using a fresh request from the intended Fuxam account.
A response says it is partial
Some reads combine several Fuxam sections. If an optional upstream section is unavailable, the MCP returns the sections it could retrieve and identifies what can be retried.
FAQ
Do I need to install Node.js, Playwright, or a local MCP package?
No. This is a hosted Streamable HTTP MCP. Add the production URL to your client and complete browser authorization; there is no local Fuxam runtime to install.
Can I paste the copied cURL request into my AI chat?
No. It contains your Fuxam session cookie. Paste it only into the Fuxam Student MCP authorization page. The page extracts the exact __client cookie and discards the other copied headers and cookies.
Will I need to authorize every time I use it?
No. Reauthorize only when the stored Fuxam session expires, is revoked, or belongs to a different active account. A normal new chat can reuse the existing MCP authorization.
Can the MCP change my Fuxam account?
Only the four explicit booking and waitlist tools can change account state. Your agent should ask before using them, and the MCP verifies the resulting Fuxam state. All other tools are read-only.
Where do I send feedback or request a feature?
Message Max on CODE Slack with bugs, setup problems, feedback, or ideas for new tools. For errors, include the client name, the exact error code or message, and the step that failed. Never send the copied cURL request, __client cookie, OAuth token, or authorization headers.
Privacy and analytics
The Privacy Policy explains how the hosted service processes account, academic, authentication, and usage data. The Terms cover use of the service. Both are linked directly from the authorization screen.
Status
Fuxam Student MCP is an unofficial student-built service.
Updated 11 days ago