Skip to main content
Glama
737,333 tools. Updated 2026-11-02 20:18

"A server for managing Upwork-related tasks with MCP" matching MCP tools:

  • Who am I? Returns the signed-in account: email, @handle, plan + limits, counts of sites/domains/drives, and connected DNS providers. Call this first to orient before managing sites or domains.
    ConnectorNo auth
  • Get a Stripe billing portal URL for managing payment methods and invoices. Returns a URL (not a redirect) that the human can open in a browser. Requires: API key with read scope. Args: flow: Optional. Set to "payment_method_update" to go directly to the payment method update page. Returns: {"url": "https://billing.stripe.com/p/session/..."}
    ConnectorNo auth
  • One read for planning or reviewing a day: the day's tasks in display order (timed first), tasks left open the day before, repeating tasks due that day with their streak (streak_today on other days), and planned vs done for that week (Monday to Sunday). Fits for reading a day without showing it: reviewing how a day went, or answering a question about it. When the user wants to see or plan their day, show_day fits. Omit date for the user's today. Tasks of spheres the user hides from their day (Hide from my day) are left out of the tasks and of the week's planned vs done (Dashboard in the app still counts their done ones), only their number shows as hidden_from_day; get_tasks lists them.
    ConnectorOAuth
  • Read tasks from a 'todo' board with server-side filtering — handy for 'what's overdue?' / 'what's assigned to X?' without pulling the whole board. All filters are optional and AND together: `assignee` (exact match), `priority` ('H'|'M'|'L'), `done` (boolean), `overdue` (true → due_date strictly before today, not done), `due_before` / `due_after` (ISO date window on due_date). Returns `{ boardId, mode, tasks }` — tasks ordered by sort, each with the same fields as `list_tasks`.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • The official Upwork MCP server, letting AI agents connect to Upwork and act on your behalf.

  • TasksOAuth

    Quadros, pedidos, regras e métricas do trabalho

  • Create multiple tasks in a project in one action. Use this instead of calling create_task multiple times when the user asks to create several tasks at once. All tasks are created atomically — if validation fails for any item, nothing is created.
    ConnectorOAuth
  • Create a Gantt chart from a task list — no account or API key needed. YOU author the plan: list the tasks in execution order with realistic working-day durations and dependencies (0-based positions of earlier tasks; use { task, type, lag } for start-to-start/finish-to-finish links or lag). Milestones have duration 0. Only add a dependency where a task truly needs another one finished - independent tasks should run in PARALLEL (share a predecessor, or take no dependencies at all and start at the project start). Group tasks into top-level phases for a structured plan/WBS: the phase task gets isPhase: true, its tasks get parent = the position of the phase. LoopGantt schedules it with its critical-path engine and returns a picture of the chart, the dates, the critical path and a link where the user can view, export (PNG/PDF) and save the chart. Always show the user the link. Tasks with a due date take deadline: YYYY-MM-DD (a marker - the reply reports the fit). Use create_gantt when the user wants a chart to open, export or save; use schedule_project instead for what-if date math where nothing should be stored.
    ConnectorNo auth
  • List the caller's deliberation sessions, optionally filtered by status. Most useful for agents managing multiple concurrent sessions — use `status: 'ready'` to find sessions awaiting your next round. Returns a lightweight list (no response bodies); call `get_session` for full content.
    ConnectorNo auth
  • <summary>List CRM tasks (the Tasks view), earliest due first, undated last. Tasks are shared across the user's team. Use this for "what's on my plate", "what's overdue", "what's next with Acme", and to find a task's id before update_crm_task. Follow-up suggestions Sliq proposed but the user hasn't added are not included.</summary> <returns> <description>Dict with paging info and the tasks page. {total, has_more, tasks: [{id, title, notes, due_at, status, completed_at, assignee_email, person_profile_id, company_profile_id, deal_id, person_profile, company_profile, deal (the linked deal, or null; its open_task_count and next_task aren't filled in here — use query_deals for those), data, created_at, archived_at}]}.</description> </returns>
    ConnectorOAuth
  • Returns the issue trackers connected to a team (Jira, Linear) and what each of them can do: search for tasks, list iterations (sprints, cycles), write estimates back. Call this first — the other poker tools depend on what is connected. An empty list means tasks can only be added manually with poker.game.tasks.add.
    ConnectorNo auth
  • Pause a Batch job's current run: it picks up no new tasks until batch_resume. Tasks already in flight still finish and bill; for a hard cost stop use batch_cancel. A paused run still counts as an active job. Idempotent; a run that already ended answers with its final status and already_ended:true.
    ConnectorOAuth
  • Change the task type for many tasks at once (≤5000 per call). `taskIdentifiers` are stable wire identifiers (e.g. tsk_…) — task keys (PROJ-42) are NOT accepted here; use pm_search_tasks first if you only have keys. `taskType` is a name (e.g. "Bug") or null to clear the type. Returns 200 sync for ≤500 tasks; 202 with a {jobId, statusUrl} for larger batches — poll the statusUrl for completion. API-key scope: `tasks:write`.
    Connector
    Destructive
    No auth
  • Change the task type for many tasks at once (≤5000 per call). `taskIdentifiers` are stable wire identifiers (e.g. tsk_…) — task keys (PROJ-42) are NOT accepted here; use pm_search_tasks first if you only have keys. `taskType` is a name (e.g. "Bug") or null to clear the type. Returns 200 sync for ≤500 tasks; 202 with a {jobId, statusUrl} for larger batches — poll the statusUrl for completion. API-key scope: `tasks:write`.
    Connector
    Destructive
    No auth
  • Turn a checklist into tasks for one person, each due its due_days from their start date (onboarding) or last day (offboarding), which must be set. Refused while they still have open tasks from the same checklist. Returns the tasks with their task_id. Costs $0.01 per call; nothing if it fails.
    ConnectorOAuth
  • Archive a task, or several at once with `tasks` (max 50). They move to the Trash view, out of every working list, and stay readable there (task_list `view: "trash"`). Archiving is not completing: use task_done for work that was finished, and task_archive only for tasks the user wants gone. Confirm with the user first.
    Connector
    Destructive
    No auth
  • Archive a task, or several at once with `tasks` (max 50). They move to the Trash view, out of every working list, and stay readable there (task_list `view: "trash"`). Archiving is not completing: use task_done for work that was finished, and task_archive only for tasks the user wants gone. Confirm with the user first.
    Connector
    Destructive
    No auth
  • Use this when the user explicitly asks to create or modify multiple Familia tasks, list tasks, plans, or task attachments in one request, or when one prompt contains multiple standalone dated actions that should become separate tasks. When the same task or plan repeats, use repeatRule/rrule on one operation instead of creating duplicate one-time operations. For a main event/trip plus clearly related dated actions, prefer one create_plan operation with relatedTasks. Internally this runs bounded individual write operations one by one; it does not create a backend transaction. Operations can queue assignment notifications and reminders; delivered notifications cannot be recalled.
    Connector
    Destructive
    No auth
  • Convert an Upwork job search link (upwork.com/nx/search/jobs/?...) into flconsole filters. Use it when the user already has a search on Upwork; pass the result to preview_filters, find_jobs or create_feed. Read-only. 30 calls per hour.
    ConnectorOAuth
  • Stop a Batch job's current run for good. No task still waiting is started or billed; tasks already in flight finish (and bill). Results so far stay readable with batch_results. Tasks that never started stay pending: batch_rerun (default failed and pending) runs them later. Idempotent: a run that already ended answers with its final status and already_ended:true. To halt without ending the run, use batch_pause.
    Connector
    Destructive
    OAuth
  • WHEN: You can take an offered work contract for your swarm. DO: Take an offered work contract for your swarm. POST /api/v1/tasks/{id}/claim with assignee_id. No API key. HTTP 409 means another agent already claimed it. List offered tasks with GET /api/v1/tasks?status=offered first. Store claim_token. DON'T: Claim a contract you published, or retry a 409 on the same id. NEXT: complete_task with claim_token and result_payload.
    ConnectorNo auth