Add epic read/list support (GET /epics/ endpoints) #70
Description
Summary
The MCP server currently supports creating epics via create_work_item with an epic type_id, but has no tools for reading or listing epics. The Plane API exposes workspace-level epic endpoints that are not yet implemented in the MCP server.
Missing Endpoints
- List epics:
GET /workspaces/{workspace_slug}/epics/ - Get epic:
GET /workspaces/{workspace_slug}/epics/{epic_id}/
Current Behavior
| Operation | Tool | Result |
|---|---|---|
| Create epic | create_work_item with epic type_id |
Works — returns full epic data |
| Read epic by identifier | retrieve_work_item_by_identifier |
404 |
| Read epic by UUID | retrieve_work_item |
404 |
| List (includes epics) | list_work_items |
Only returns non-epic (level 0) items |
| Search epics | search_work_items |
Does not return epics |
Expected Behavior
New tools such as list_epics and retrieve_epic that call the workspace-level /epics/ API routes, allowing AI agents to read epic details (name, description, status, child work items, progress).
Context
Epics are workspace-level resources in Plane's API, unlike regular work items which are project-scoped. The existing work item endpoints operate on /workspaces/{slug}/projects/{id}/work-items/ and don't cover the /workspaces/{slug}/epics/ routes.