@tasque/piazza-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@tasque/piazza-mcp List my courses"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@tasque/piazza-mcp
MCP server for Piazza Q&A platform via reverse-engineered internal API.
Warning — Piazza has no public API. This uses reverse-engineered endpoints that may break or violate their Terms of Service.
Tools
Tool | Description |
| List all enrolled Piazza courses |
| Get detailed course info |
| Get course statistics |
| Get full post with answers and follow-ups |
| Get recent posts feed with pagination |
| Search posts by keyword |
| Filter feed by folder, following, or unread |
| Create a question, note, or poll |
| Add a follow-up to a post |
| Reply to a follow-up |
| Post or update the student answer |
| Post or update the instructor answer |
| Endorse an answer or follow-up |
| Remove an endorsement |
| Edit a post's title or content |
| Delete a post (instructor/TA only) |
| Pin or unpin a post |
| Mark a post as duplicate |
| Mark a question as resolved |
| Mark a post as read |
| List all course members |
| Get user profiles by ID |
Related MCP server: canvas-lms
Environment Variables
Variable | Required | Description |
| Yes | Piazza account email |
| Yes | Piazza account password |
Auth Setup
Set both environment variables. The server authenticates via form-based login with CSRF token extraction. Sessions are maintained in memory with automatic re-authentication on 401/403.
Development
npm install
npm run build
npm start # stdio modeAvailable Tools
22 toolscreate_followupC
Create a follow-up discussion on an existing Piazza post.
Inputs: content (required), network_id (required), post_number (required), anonymous.
create_postA
Create a new post (question, note, or poll) in a Piazza course.
Inputs: type (required), title (required), content (required), network_id (required), +2 more.
create_replyB
Reply to a follow-up discussion on a Piazza post.
Inputs: content (required), network_id (required), followup_id (required), post_number (required), +1 more.
delete_postA
Delete a Piazza post. This action is destructive and cannot be undone. Requires instructor/TA privileges.
Inputs: network_id (required), post_number (required).
edit_postA
Edit the title or content of an existing Piazza post. You must provide at least one of title or content.
Inputs: network_id (required), post_number (required), title, content.
filter_postsB
Filter the post feed by folder, following status, or unread status.
Inputs: network_id (required), folder, unread, following.
get_course_infoA
Get detailed information about a specific Piazza course/network including folders, instructors, term, and settings.
Inputs: network_id (required).
get_course_statsB
Get statistics for a Piazza course including participation data, post counts, and response metrics.
Inputs: network_id (required).
get_feedA
Get the feed of recent posts in a Piazza course, sorted by most recently updated. Supports pagination.
Inputs: network_id (required), limit, offset.
get_postA
Get a full Piazza post including the question body, all answers (student and instructor), follow-up discussions, and endorsements. Use the post number (e.g. '123' for @123).
Inputs: network_id (required), post_number (required).
get_user_profileA
Get profile information for specific users in a Piazza course by their user IDs.
Inputs: user_ids (required), network_id (required).
list_coursesA
List all Piazza courses/networks the authenticated user is enrolled in. Returns course names, IDs, terms, and roles.
Inputs: no named parameters.
list_usersA
List all users (students, instructors, TAs) in a Piazza course with their names, emails, and roles.
Inputs: network_id (required).
mark_answer_goodA
Mark an answer or follow-up as 'good answer' (endorse it). This is equivalent to the 'good answer' button on Piazza.
Inputs: type (required), network_id (required), post_number (required).
mark_duplicateA
Mark a Piazza post as a duplicate of another post. The duplicate will link to the original.
Inputs: network_id (required), original_post (required), duplicate_post (required), message.
mark_readA
Mark a Piazza post as read.
Inputs: network_id (required), post_number (required).
mark_resolvedB
Mark a Piazza question as resolved or unresolved.
Inputs: network_id (required), post_number (required), resolved.
pin_postA
Pin or unpin a Piazza post. Pinned posts appear at the top of the feed.
Inputs: network_id (required), post_number (required), pin.
post_instructor_answerA
Post or update the instructor answer on a Piazza question. Requires instructor/TA privileges.
Inputs: content (required), network_id (required), post_number (required), revision, +1 more.
post_student_answerA
Post or update the student answer on a Piazza question. The student answer is a collaborative wiki-style answer that any student can edit.
Inputs: content (required), network_id (required), post_number (required), revision, +1 more.
remove_answer_goodA
Remove a 'good answer' endorsement from an answer or follow-up.
Inputs: type (required), network_id (required), post_number (required).
search_postsA
Search for posts in a Piazza course by keyword. Returns matching posts with their numbers and subjects.
Inputs: query (required), network_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 22 tools
Each tool targets a distinct Piazza resource and action: courses, posts, users, follow-ups, answers, endorsements, and moderation flags. Even similar-appearing tools like get_course_stats vs get_course_info are clearly differentiated by their descriptions.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_courses, create_post, mark_resolved). Minor variation between get_ and list_ is conventional and predictable.
22 tools is slightly above the typical 3-15 ideal range, but each tool corresponds to a meaningful Piazza interaction. The number is justified by the breadth of the platform's features, though a few could potentially be combined (e.g., mark_read with edit_post).
The tool set covers the full lifecycle of Piazza posts (create, read, update, delete, moderate), user browsing, and course info. It includes answer posting, follow-ups, endorsements, and status management, leaving no obvious dead ends for common workflows.
Related MCP Connectors
Read-only MCP server for ClassQuill, a tutoring-business-management platform.
Public MCP server for discovering open jobs. Search, filter, and get application links.
The official MCP Server for the Mux API
The official Planning Center MCP server for interacting with your ministry's data.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that automates login to PAUSD Schoology via ClassLink and provides tools to fetch grades, upcoming assignments, and recent posts.1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Canvas LMS with automatic OAuth authentication. Enables interaction with courses, assignments, grades, modules, discussions, quizzes, files, calendar, messaging, and more without manual API token management.2MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that connects AI assistants to university D2L Brightspace and Piazza, enabling query of courses, grades, assignments, deadlines, files, and Piazza posts.7MIT
- AlicenseBqualityDmaintenanceMCP server for Universidade de São Paulo's student systems (Moodle, JupiterWeb) enabling assistants to query grades, schedule, tasks, and more via secure backend.205GPL 3.0