Edworking

@Edworking list all tasks in the Q1 Launch project and show me which ones are overdue or blocked

Retrieved 23 tasks from the Q1 Launch project. 4 tasks are overdue: 'Finalize pricing page copy' (due Jan 15, assigned to Sarah), 'Set up analytics tracking' (due Jan 18, assigned to Mike), 'Review legal terms' (due Jan 12, unassigned), and 'Export customer testimonials' (due Jan 10, assigned to Jordan). 2 tasks are in 'Blocked' state: 'Deploy staging environment' (waiting on DevOps approval) and 'Schedule launch webinar' (pending marketing budget sign-off). The remaining 17 tasks are on track across 'In Progress' and 'To Do' states.

This read-heavy example demonstrates the MCP's ability to fetch task lists and synthesize status information. Requires API key with read access to the target project. The MCP returns raw task data; the AI performs the filtering and categorization logic based on due dates and state fields.

@Edworking create a task called 'Draft onboarding email sequence' in the Marketing Automation project, assign it to Emma, and set the due date to next Friday

Created task 'Draft onboarding email sequence' in the Marketing Automation project (ID: proj_8x2k9). Task ID: task_4m7n3. Assigned to Emma Chen. Due date set to January 24, 2025. The task is currently in 'To Do' state. Note: Edworking's API does not directly support due date assignment during task creation; you may need to update the task separately or configure due dates through the Edworking web interface if this field was not persisted.

This write example shows task creation with assignment. The MCP can create tasks and set basic fields, but Edworking's API has limitations around certain metadata like due dates depending on your workspace configuration. Always verify critical fields were set by fetching the task afterward if automation depends on them.

@Edworking review all time entries logged this week across the Client Services project and calculate total billable hours by team member

Analyzed 47 time entries from the Client Services project (Jan 13-19, 2025). Total billable hours by team member: Alex Rodriguez: 28.5 hours (largest block: 6 hours on 'Q4 report finalization'), Jordan Kim: 22 hours (primarily 'Client onboarding calls'), Sam Patel: 19.5 hours (mix of 'Support tickets' and 'Documentation updates'), Taylor Morgan: 15 hours (focused on 'Strategy workshop prep'). Combined team total: 85 billable hours this week. Three entries lack task associations and may need manual review for invoicing accuracy.

This synthesis example pairs the MCP's time-entry retrieval with AI aggregation logic. Useful for weekly reporting or invoice prep. The MCP fetches raw time records; the AI performs the grouping and math. Be aware that time entries are tied to tasks, so orphaned or deleted tasks may cause gaps in historical reporting.

When Edworking MCP fits distributed contractor billing

A 6-person agency with three contractors bills clients by the hour and needs timestamped entries tied to specific tasks. The Edworking MCP wins here because Add Time Entry writes duration and start time in one call, and Get Task pulls the full audit trail without switching apps. The 12-tool scope covers task creation, folder navigation, and project listing—enough to automate weekly invoice prep from a Switchy prompt. The trade-off: if you need rich chat history or file attachments, List Messages returns activity records that don't reliably map to conversational threads, so you'll still open the Edworking UI for context. If your billing cycle is weekly and your contractors log time daily, this MCP cuts the manual export step and keeps your finance workflow in one workspace.

Why this MCP struggles with knowledge transfer at scale

A 10-person consultancy wraps a six-month client engagement and wants to package all tasks, states, and folder structure into a handoff doc. The Edworking MCP can list projects, enumerate folders, and pull individual tasks, but it lacks bulk export or recursive folder traversal—you'll write a loop that calls List Folders and Get Task hundreds of times. For a project with 200 tasks across 15 folders, that's slow and token-heavy in a Switchy session. The MCP is better suited to spot checks ("show me all tasks assigned to Sarah in the Q1 folder") than full-project snapshots. If your handoff is under 50 tasks or you only need a subset filtered by assignee or state, the MCP works. Beyond that threshold, export from Edworking's UI and upload the CSV to Switchy for summarization instead.

When this MCP speeds up daily team check-ins

A 4-person product team runs 15-minute standups and needs to see who's blocked, what shipped yesterday, and what's in progress today. The Edworking MCP handles this cleanly: List Projects finds the active sprint, List Project States confirms your workflow labels, and Get Task pulls assignee and state for each item on the board. You can prompt Switchy to generate a standup summary in under 30 seconds without opening Edworking. The API key auth means the whole team shares one connection, so no per-seat OAuth friction. The limit: if your standup references message threads or file uploads, List Messages won't give you the conversational context—you'll still need the Edworking UI for "what did the client say about that bug?" For status-only standups under 20 tasks, this MCP keeps the meeting moving and the context in Switchy.