settings_input_componentIntegrations

Integrations with GitHub, Jira and invoicing — ending in an invoice, not a closed ticket.

The only tool where integrations close the whole cycle: task → commit → merge → work report → invoice. No manual retyping, no middleware.

Connectors: inbound webhooks from GitHub and GitLab · pull requests opened by the runner on GitHub or Bitbucket Cloud · import from Jira and Trello · export to Czech invoicing.

Who this is for

check_circle

You bill clients by hours logged

Commit → work report → invoice in Fakturoid or iDoklad, without retyping hours or copying totals.

check_circle

You don't want a big migration project

Two-way coexistence with Jira, Trello, or EasyRedmine. Move over when you're ready; leave any time.

From commit to invoice — automatically

Competitors end when the PR closes the ticket. mcptask.online keeps going until the invoice is issued.

1

Commit with %

A commit message like https://mcptask.online/ACCOUNT/tasks/47 40% updates the piece automatically.

2

Piece advances

The linked task moves forward and the effort is logged — no one opens the board to drag cards.

3

PR / MR merged

Merge triggers approval and a completion note. The last effort is set to 100%.

4

Work report ready

Reported time is collected into a clean work report for the period and client.

5

Invoice issued

One click creates the invoice in Fakturoid or iDoklad, with VAT and client mapping handled.

auto_awesome

Others stop at 'ticket closed'. mcptask.online stops at 'invoice sent'.

Setup takes 5 minutes. No middleware, no scraping, no custom code.

Version control (Inbound webhooks)

These are inbound webhooks — your Git host calls mcptask.online when something happens. The direction reverses for pull requests: the runner's mcptask_runner pr command goes outbound and opens, reviews and merges PRs on GitHub or Bitbucket Cloud. Outbound webhooks (mcptask.online → your systems) are planned; see the roadmap.

code

GitHub Integration

check_circleLive (Inbound Webhooks)schedule5 minutes

Commits and PRs automatically update the linked piece and trigger approval on merge.

  • checkTwo webhooks per repository — one for push, one for pull request
  • checkCommit message progress + PR body reference → auto-approval on merge
  • checkWorks with public and private repositories
  • checkSigned with your account secret token via X-Hub-Signature-256
code

GitLab Integration

check_circleLive (Inbound Webhooks)schedule5 minutes

Commits and MRs automatically update the linked piece and trigger approval on merge.

  • checkTwo webhooks per project — one for push, one for merge request
  • checkCommit message progress + MR description reference → auto-approval on merge
  • checkWorks with GitLab.com and self-hosted GitLab (12.0+)
  • checkAuthenticated by the X-Gitlab-Token header (your account's secret token)
call_made

Bitbucket Cloud — via mcptask_runner

check_circleLive (outbound, via runner)schedule5 minutes

The runner opens, reviews, checks and merges pull requests on Bitbucket Cloud — mcptask_runner pr drives the whole PR loop from the piece.

  • checkPR create / list / view / reviews / merge / checks — all driven by the runner through mcptask_runner pr
  • checkCredential: a Bitbucket access token, or email + API token (app passwords are refused)
  • checkgit_host is derived from the repository remote, or set explicitly with mcptask_runner init --git-host bitbucket
blockNo inbound webhooks yet — commit/PR ↔ piece pairing and the timeline stay GitHub/GitLab only

Run your project from chat — no terminal, no new UI

Paste one URL into Claude Cowork or claude.ai and you can plan, log time, and reply to clients straight from the conversation. OAuth 2.0 — no token, no config file.

link

Remote MCP server URL

https://mcptask.online/mcp

Paste this URL into Customize → Connectors → Add custom connector in Cowork / claude.ai

Using Claude Cowork or claude.ai? Connect in 2 minutes with one URL — no terminal, no new dashboard.

  1. 1

    Create an account

    30-day free trial, no card.

  2. 2

    Paste the URL

    One URL, no token, no Client ID.

  3. 3

    Approve and chat

    OAuth in your browser, then chat.

menu_bookDetailed steps
expand_more
groups

On a Team or Enterprise plan?

An Owner first adds the connector in Organization settings → Connectors (https://claude.ai/admin-settings/connectors): Add → hover Custom → Web → paste the URL → Add. Each member then connects it themselves in Customize → Connectors — it carries a Custom label.

cloud

Heads up on architecture

The connection originates from Anthropic's cloud infrastructure, not from your machine. That is also true for Cowork and Claude Desktop. mcptask.online is publicly reachable, so no firewall or VPN setup is required.

  1. Create your mcptask.online account

    Free 30-day trial, no card. You can do this right now in a different tab.

    person_addCreate account

  2. Be logged in

    The OAuth approval happens in this browser, so the account you just created has to be the active session here.

    loginLog in

  3. Open Customize → Connectors in Cowork / claude.ai

    In Cowork or claude.ai, go to https://claude.ai/customize/connectors. Click the + and choose Add custom connector.

  4. Paste the mcptask.online URL

    Paste this URL — no Client ID or Secret, no token. Dynamic client registration handles the rest.

    linkRemote MCP server URL
    https://mcptask.online/mcp

  5. Click Connect and approve

    Click Connect. Your browser opens the mcptask.online OAuth approval page — log in (if you aren't already) and click Authorize. No token, no password is shared with Anthropic.

  6. Enable the connector in your chat

    In a new chat, click + (lower left), choose Connectors and toggle mcptask.online on. Try a first prompt:

    List my projects and my next task.

Invoicing & Billing

receipt_long

Fakturoid (Czech Republic)

check_circleLiveverifiedAll Plans

Features

  • checkOAuth 2.0 authentication
  • checkIssue invoice from work report
  • checkAutomatic VAT calculation (CZ rates)
  • checkClient mapping (Fakturoid contact ↔ mcptask.online company)
  • checkSet taxable supply and invoice date based on reported time

Workflow

  1. 1Reports → Work report
  2. 2Select company, period from the 1st to the end of the month
  3. 3Click "Issue invoice to Fakturoid"
  4. 4Invoice is created in Fakturoid
scheduleSetup Time: 5 minutes
receipt_long

iDoklad (Czech Republic)

check_circleLiveverifiedAll Plans

Features

  • checkOAuth 2.0 authentication
  • checkIssue invoice from work report
  • checkAutomatic VAT calculation (CZ rates)
  • checkClient mapping (iDoklad contact ↔ mcptask.online company)
  • checkSet taxable supply and invoice date based on reported time

Workflow

  1. 1Reports → Work report
  2. 2Select company, period from the 1st to the end of the month
  3. 3Click "Issue invoice on iDoklad"
  4. 4Invoice is created in iDoklad
scheduleSetup Time: 5 minutes
info

Note — Stripe (our own billing)

Stripe is only used to bill you for your mcptask.online subscription (per-seat Starter/Professional/Enterprise). It is not a way to bill your clients through mcptask.online — use Fakturoid or iDoklad above for that. Details on the Pricing page.

Coexistence & migration

Coexist with the tools you already have. Sync both ways, then leave only when you want to.

work

Jira

check_circleLiveverifiedAll Plans

Two-way sync with Jira Cloud or self-hosted via per-project API token. Comments, efforts, and finish events mirror the linked issue.

  • checkTwo-way sync: export to Jira, import Jira issues back
  • checkPer-project: base URL + project key + per-user API token
  • checkJira issue key prefix (PROJ-123) keeps the link both ways
dashboard

Trello

check_circleLiveverifiedAll Plans

Export any task to a Trello card; import a card by name; comments and efforts sync back to the card.

  • checkExport to a single Trello board per project
  • checkTwo-way sync for comments, efforts, finish events
  • checkPer-user OAuth via the Trello API token
view_kanban

EasyRedmine

check_circleLiveverifiedAll Plans

Two-way sync with self-hosted EasyRedmine. Difficulty custom field on the issue mirrors the piece's scrum point.

  • checkTwo-way sync: export to EasyRedmine, import issues back
  • checkPer-project: base URL + project ID + per-user API key
  • checkWorks for any piece type (Epic, Story, Task, Recurent)

A PM Tool the Agent Drives

mcptask.online is built MCP-first. The agent doesn't just read your tasks — it uses the workspace as its work queue: GetNextTaskTool → work → LogWorkProgressTool → AddMessageTool.

What an autonomous workflow looks like

Plug in an MCP client and the workspace becomes the agent's to-do list, progress log, and hand-off channel.

check_circleWorkspace = the agent's work queue (MCP-first PM tool).
check_circleEvery action is scoped to the user's permissions and logged under their name.
open_in_newmcptask_runner uses this MCP server as its work queue

What is MCP?

mcptask.online is built so your AI assistant can drive the whole workspace through MCP — speak one protocol, get the full tool surface (list, read, create, log, message). No HTML to scrape, no bespoke HTTP per integration. For a one-paragraph definition of the acronym, see the glossary below.

Open the glossary

check_circleAI understands data structure immediately
check_circleNo custom integration code needed
check_circleReliable, versioned protocol
check_circleSame interface for all MCP clients

What you can do over MCP

Read:

  • visibilityList projects and pieces (tasks/stories/epics)
  • visibilityGet piece details (description, status, history)
  • visibilityView parent/child relationships
  • visibilityAccess comments and attachments
  • visibilityView work performed

Write:

  • editUpdate piece status
  • editLog work efforts
  • editAdd comments
  • editAttach files
  • editCreate pieces and subtasks

Query:

  • searchGet next available piece (priority-sorted)
  • searchFilter pieces by project, status, type
  • searchList recent activity

Priority Factors

Priority levelUrgent > High > Normal > Low
Due datesooner = higher priority
Task typebugs before features, configurable
Ageolder tasks surface
publicAny System

Connect Any AI Agent via MCP

mcptask_runner is optional. Any MCP-capable AI agent — Claude Code, Claude Desktop, Copilot in your IDE, or any other client — can read and work your tasks directly, no autonomous loop required. No binary, no install, just a tiny config file.

If your AI client speaks MCP, the connection takes about two minutes: get a token, add one server entry, and tell your agent which project to work on. The acronym MCP is explained in the glossary a few sections below. Open the glossary

Which clients work?

Anything that speaks MCP. Each row carries the date it was last re-checked.

Claude Code (CLI)

Works

Best fit. Add the server to your .mcp.json and Claude Code can read, list, and create tasks.

Verified 2026-08

Claude Desktop

Works

Add the same server entry to Claude Desktop's MCP settings. Same token, same endpoint.

Verified 2026-08

Other MCP clients

Works

Any client that accepts the standard MCP server config (VS Code Continue, Cursor when MCP-enabled, custom agents) works the same way.

Verified 2026-08

GitHub Copilot (IDE: VS Code, JetBrains, Eclipse, Xcode)

Works

Copilot speaks MCP natively in the IDE and supports custom MCP servers. Add the same .mcp.json entry as Claude Code.

Verified 2026-08

GitHub Copilot (github.com/copilot web)

Not supported

The web chat at github.com/copilot cannot connect custom MCP servers, so mcptask cannot be wired in there.

Verified 2026-08

GitHub Copilot (cloud agent / code review)

Partial

MCP tools work, but MCP resources and prompts do not. A large part of mcptask's surface is served as resources under mcptask:// URIs, so resource reads fail there.

Verified 2026-08

mcptask.online as Your Agent's Task Queue

The Agent Workflow

1

Agent calls GetNextTaskTool via MCP

arrow_downward
2

mcptask.online returns highest priority task

arrow_downward
3

Agent works on task (coding, testing, etc.)

arrow_downward
4

Agent calls LogWorkProgressTool with progress

arrow_downward
5

Agent logs 100% via LogWorkProgressTool: mcptask.online marks the task complete on its own

arrow_downward
6

Loop: Agent calls GetNextTaskTool again

check

Task locking prevents duplicate work

check

Priority-based task selection

check

Effort logging in a single tool call

check

Completion follows from a hundred-percent progress

check

Continuous operation loop

For Developers

No middleware, no scraping, no fictional endpoints. Set up in 5 minutes and drive mcptask.online from your AI client, Git host, or server script.

  • account_circleClaude Cowork / claude.ai — detailed OAuth walkthrougharrow_upward
  • codeGitHub webhooks — push + pull request

    GitHub Integration

    check_circleLive (Inbound Webhooks)schedule5 minutes

    Features

    codeWebhook event processing (push, pull request)
    codeTwo repository webhooks — one for push events, one for pull request events
    codeCommit messages link work to a piece and set its progress percentage
    codePull request body references link the PR and approve the piece on merge
    codeSigned with your account secret token via X-Hub-Signature-256

    How it works

    1. 1Copy your account secret token from mcptask.online (Account → Integrations).
    2. 2In your GitHub repository, add a webhook with Payload URL https://mcptask.online/github/efforts, select Just the push event, and paste the secret token.
    3. 3Add a second webhook with Payload URL https://mcptask.online/github/pulls, select Let me select individual events → Pull requests, and paste the same secret token.
    4. 4In commit messages, add a line https://mcptask.online/ACCOUNT/tasks/ID NN% where NN is the progress percentage.
    5. 5In pull request descriptions, add a line mcptask: https://mcptask.online/ACCOUNT/tasks/ID.
    6. 6When the PR is merged, the referenced piece is approved and the last effort is set to 100%.

    How to reference a piece

    Use the piece's public URL https://mcptask.online/ACCOUNT/tasks/ID. ACCOUNT is your account code and ID is the piece's relative ID shown on the piece page and in the URL.

    Examples:

     https://mcptask.online/ACCOUNT/tasks/47 40%https://mcptask.online/ACCOUNT/tasks/48 100%mcptask: https://mcptask.online/ACCOUNT/tasks/47

    Pull Request Integration

    • mergePR opened → a note with the PR link is added to the piece
    • mergePR merged → the piece is approved and a completion note is added
    • mergeThe last effort's progress is set to 100% on merge
    • mergeWorks with any public or private repository that can reach mcptask.online

    Configuration

    settingsTwo webhooks per repository (separate endpoints for push and pull request events)
    settingsPrivate repository support
    settingsNo source code access — only webhook metadata is processed
    settingsTLS required
  • codeGitLab webhooks — push + merge request

    GitLab Integration

    check_circleLive (Inbound Webhooks)schedule5 minutes

    Features

    codeTwo project webhooks — one for push events, one for merge request events
    codeCommit messages link work to a piece and set its progress percentage
    codeMerge request description references link the MR and approve the piece on merge
    codeAuthenticated by the X-Gitlab-Token header (your account's secret token)

    How it works

    1. 1Copy your account secret token from mcptask.online (Account → Integrations).
    2. 2In your GitLab project, add a webhook with URL https://mcptask.online/gitlab/efforts, trigger Push events, and paste the secret token into the Secret token field.
    3. 3Add a second webhook with URL https://mcptask.online/gitlab/merge_requests, trigger Merge request events, and use the same secret token.
    4. 4In commit messages, add a line https://mcptask.online/ACCOUNT/tasks/ID NN% where NN is the progress percentage.
    5. 5In merge request descriptions, add a line mcptask: https://mcptask.online/ACCOUNT/tasks/ID.
    6. 6When the MR is merged, the referenced piece is approved and the last effort is set to 100%.

    How to reference a piece

    Use the piece's public URL https://mcptask.online/ACCOUNT/tasks/ID. ACCOUNT is your account code and ID is the piece's relative ID shown on the piece page and in the URL.

    Examples:

     https://mcptask.online/ACCOUNT/tasks/47 40%https://mcptask.online/ACCOUNT/tasks/48 100%mcptask: https://mcptask.online/ACCOUNT/tasks/47

    Merge Request Integration

    • mergeMR opened → a note with the MR link is added to the piece
    • mergeMR merged → the piece is approved and a completion note is added
    • mergeThe last effort's progress is set to 100% on merge
    • mergeWorks with GitLab.com and self-hosted GitLab (12.0+) that can reach mcptask.online

    Configuration

    settingsTwo webhooks per project (separate endpoints for push and merge request events)
    settingsSelf-hosted GitLab support (12.0+)
    settingsNo source code access — only webhook metadata is processed
    settingsTLS required
  • call_madeBitbucket Cloud — runner-side PRs (mcptask_runner pr), no webhooksarrow_upward
  • terminalREST API — JSON over HTTP

    REST API

    check_circleLive (Stable)workspace_premiumProfessional, Enterprise

    JSON over HTTP, scoped to your account. Use it when MCP isn't a fit (server-to-server scripts, dashboards, non-MCP tools).

    Authentication

    One credential, one header. The same MCPTASK_TOKEN you use for the MCP server authenticates every REST API call as a Bearer token.

    codeHeader
    Authorization: Bearer <MCPTASK_TOKEN>

    Get a token in mcptask.online → View user → Advanced info → API Token. JWT-encoded, signed with HS256, scoped to your user — no separate API key, no per-account rotation.

    Endpoints

    All endpoints are scoped to your account code (the short code from your mcptask.online URL). Real paths use /pieces (the generic term) rather than /tasks — we use "piece" as the umbrella word for task, story, epic, recurent.

    Projects
    codeGET /api/{account_code}/projects - List projects
    Pieces (Tasks, Stories, Epics, Recurents)
    codeGET /api/{account_code}/pieces/{id} - Get piece
    codePOST /api/{account_code}/pieces - Create piece
    Efforts
    codeGET /api/{account_code}/pieces/{id}/efforts - List efforts
    codePOST /api/{account_code}/pieces/{id}/efforts - Log effort
    Users
    codeGET /api/{account_code}/users/{id} - Get user
    codeGET /api/{account_code}/users/current - Current user

    Rate Limits

    Enforced per account and per token: 60 requests/minute per token, plus the hourly per-account cap below, shared by the MCP server and the REST API. Contact us if you need a higher ceiling.

    Starter
    1,000/hour
    Professional
    10,000/hour
    Enterprise
    Custom

    The REST API itself is a Professional and Enterprise feature — the Starter cap applies to the MCP server.

    Documentation

    Real calls you can paste in a terminal right now. Replace $MCPTASK_TOKEN with a token from View user → Advanced info → API Token and $ACCOUNT with your account code.

    codeCheck API version (no token needed)
    curl https://mcptask.online/api
    Response
    { "message": "mcptask.online REST API v0.10", "version": "0.10", "version_app": "5.72", "revision": "1272" }
    codeIdentify the current user
    curl https://mcptask.online/api/$ACCOUNT/users/current \
  -H "Authorization: Bearer $MCPTASK_TOKEN"
    Response
    { "id": 7, "user_nick": "george", "email": "george@example.com", "default_account_code": "bcp" }
    codeList your projects
    curl https://mcptask.online/api/$ACCOUNT/projects \
  -H "Authorization: Bearer $MCPTASK_TOKEN"
    Response
    [ { "id": 1, "code": "bcp", "name": "BCP Development" } ]
    codeCreate a piece (Task)
    curl -X POST https://mcptask.online/api/$ACCOUNT/pieces \
  -H "Authorization: Bearer $MCPTASK_TOKEN" \
  -H "Content-Type: application/json" \
  -d ''{"piece_type":"Task","name":"Review PR","project_id":1}''
    Response
    { "id": 42, "name": "Review PR", "piece_type": "Task", "state": "new" }
  • menu_bookQuick glossary

    Quick glossary

    A few terms used across this page, in plain English.

    MCP

    Model Context Protocol — a standard way AI assistants (Claude, Cursor, Cline, …) talk to external tools. mcptask.online speaks MCP natively, so any MCP client can drive it.

    SSE

    Server-Sent Events — a legacy HTTP transport that MCP used for streaming tool calls. New clients should use the current streamable HTTP transport at https://mcptask.online/mcp; the legacy SSE endpoint is still served for backwards compatibility only.

    Webhook

    An HTTP call one app makes to another when something happens. Inbound = something calls mcptask.online (e.g. GitHub on push). Outbound = mcptask.online calls your system (planned, not live yet).

    MCPTASK_TOKEN

    A long random string that proves to mcptask.online that a request really comes from you. Generate it once in mcptask.online → View user → Advanced info → API Token and use it as a Bearer token. Treat it like a password.

    Custom connector

    The claude.ai / Cowork UI for adding a remote MCP server by URL. You give it the URL, click Connect, and the OAuth flow finishes the wiring — no token to copy, no config file to edit.

  • constructionAvailable MCP tools

    Available MCP Tools

    The 22 tools below are the real ones shipped by mcptask.online's MCP server today. AddMessageTool, AddAttachmentTool, CreatePieceTool, LogWorkProgressTool and the read-side tools work end-to-end.

    ToolDescription
    AddAttachmentToolAttach a file to a piece
    AddMessageToolAdd a comment / message to a piece
    BlockTaskToolBlock or unblock a task that cannot be finished right now, with an optional reason (state only — creates no dependency between pieces)
    CreatePieceToolCreate a new piece (task, story, epic, recurent)
    ExportTimeSheetReportToolExport a timesheet report as JSON, CSV or PDF (the PDF comes back base64-encoded)
    GetAccountToolFetch account details: attributes, account-level users, permitted projects and companies
    GetAttachmentToolFetch attachment metadata and a direct download URL for a piece
    GetCurrentUserToolIdentify the user behind the current token
    GetNextStorySubtaskToolGet the next subtask to work on inside one Story
    GetNextTaskToolGet the highest-priority available task
    GetPieceEffortsToolRead time-tracking entries for a piece
    GetPieceToolFetch a single piece by ID
    GetProjectToolFetch one project's metadata
    GetProjectTreeToolGet the project hierarchy (epics/stories/tasks)
    GetUsageGuideToolSelf-describe the server (capabilities and usage hints)
    ListPiecesToolList pieces with filters (project, status, type)
    ListProjectsToolList projects you have access to
    ListTimeSheetReportOptionsToolList the filters the timesheet report accepts (companies, projects, workers, layout)
    LogWorkProgressToolLog effort on a piece and update its progress
    ManageBlockerLinksToolDeclare or clear a dependency: the piece you name waits for the blockers you list, and drops out of the next-task queue until they are done (adding is all-or-nothing — one bad id rejects the whole call)
    SendOutreachEmailToolSend a personalized outreach email from your own address (3/day, honours the suppression list and dedupe_key)
    UpdatePieceToolUpdate a piece's mutable attributes and get before/after for each one touched
  • vpn_keyAuthentication

    Authentication

    Two ways in, depending on your client. Claude Code / Cursor / Cline use a long-lived MCPTASK_TOKEN (Bearer). Claude Cowork / claude.ai use OAuth 2.0 with dynamic client registration — you never touch a token.

    MCPTASK_TOKEN (Bearer — for Claude Code, Cursor, Cline):

    • vpn_keyView user → API token in mcptask.online
    • vpn_keyTied to your user account, scoped to your workspaces
    • vpn_keyOnce and forever — no annoying periodic rotations
    • vpn_keyTreat it like a password — anyone holding it acts as you

    OAuth 2.0 (for Claude Cowork / claude.ai):

    • lockNo client secret, no manual credential — dynamic client registration
    • lockPKCE S256 — secure even on public clients
    • lockApproval is per-workspace — you pick which mcptask.online workspace the connector can act on
    • lockRevoke from claude.ai at any time (Customize → Connectors → Remove)

    Permissions:

    • securityToken inherits your user permissions — no extra scopes today
    • securityRead-only vs. read-write is controlled by the actions you call
    • securityPer-project isolation is enforced server-side
    • securityAll calls are logged under your user

FAQ

help_outline

Where do I find my MCPTASK_TOKEN?

Log in to mcptask.online, open Show user → Advanced information, and copy the API Token value (click to copy). Treat it like a password — anyone holding it acts as you on mcptask.online. To cut a client off, revoke its access in Connected applications; it will not get through on its next call.

help_outline

What address does the MCP server run on?

https://mcptask.online/mcp — streamable HTTP transport, one entry in your client config. The older SSE endpoint is still served for backwards compatibility, but point new clients at /mcp. It is not unlimited: 60 requests per minute per token plus the hourly account cap from your plan (see Rate limits above).

help_outline

Which AI tools support MCP?

Claude Code, Claude Desktop, Claude Cowork, Cursor, Cline, Continue, Codex CLI, OpenCode, and a growing list of MCP-native clients. If your tool speaks MCP, mcptask.online works with it. If not, use the REST API.

help_outline

What is a "piece"?

A piece is the umbrella name for tasks, stories, epics, and recurents. The MCP URI for a piece is mcptask://pieces/{account_code}/{piece_id} — there are no separate /tasks/ or /stories/ paths. Projects are not pieces; they have their own URI, mcptask://projects/{account_code}/{project_id}. Both take the relative ID — the number you see in the mcptask.online URL. There is no REST fallback for this: the REST API finds a piece by its internal id, so passing a relative ID to curl returns the wrong piece or a 403.

help_outline

Can an agent create pieces?

Yes, if the role of the user whose token it connects with allows it — the rule keys off role and authorship, not off who is at the keyboard. To prevent writes, give that user a read-only or limited project role; the same holds for anyone else on the team.

help_outline

Is work done over MCP visible in the log?

Yes. Every MCP action creates an event with full attribution — which user, when, what changed — flagged as arriving over MCP, so you can tell it apart from changes made in the web UI.

Planned Integrations (Roadmap)

Things we are considering. If one matters to you, mail us — high-demand items get prioritized.

webhook

Outgoing Webhooks

hourglass_empty
Coming soon
mail_outline
mcptask.online → your system event push. Email us with your use case and we'll prioritize it.
add

Missing an integration?

Request it

Request an integration: email us with your use case. We pick the next batch of integrations from real demand, not votes.

rocket_launch

Connect Your Workflow Today

Wire mcptask.online to your stack and let every commit flow into a timesheet, every review into an invoice.

Start Free TrialView the API Docs

verified_userEvery user — human or AI — is one seat. Full audit trail. 30-day trial, no credit card.