settings_input_componentIntegrations

Connect Your Entire Workflow

MCP server for AI assistants. Inbound webhooks from GitHub and GitLab. Import from Jira and Trello. Export to Czech invoicing.

MCP Server: AI's Native Language

mcptask.online provides a dedicated Model Context Protocol server — the standard way AI assistants communicate with external tools. No middleware, no scraping, no custom APIs. Native integration.

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 — the HTTP transport MCP uses for streaming tool calls. Your AI client opens a long-lived connection to our /mcp/sse URL.

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 Settings → API Access and use it as a Bearer token. Treat it like a password.

What is MCP?

MCP (Model Context Protocol) is the standard protocol AI assistants like Claude use to call external tools and read external data. Instead of parsing HTML or hand-rolling HTTP, the AI speaks MCP natively and we serve the tool definitions.

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
  • visibilityRead effort logs

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
  • searchSearch piece descriptions
  • searchList recent activity

Setup in 2 minutes

One-time setup. After this, every MCP client you connect (Claude Code, Claude Desktop, Cursor, Cline, …) can talk to mcptask.online.

  1. 1. Get your MCPTASK_TOKEN

    Log in to mcptask.online → Settings → API Access → Generate token. Copy the long string.

  2. 2. Export it in your shell

    Paste this in your terminal (or add to ~/.zshrc / ~/.bashrc so it persists):

     export MCPTASK_TOKEN=mcptask_xxxxxxxxxxxxxxxxxxxxxxxxxxxx

  3. 3. Drop this in .mcp.json (Claude Code) or your client's MCP config

    Canonical .mcp.json (Claude Code):

     {  "mcpServers": {    "mcptask-online": {      "type": "sse",      "url": "https://mcptask.online/mcp/sse",      "headers": { "Authorization": "Bearer ${MCPTASK_TOKEN}" }    }  }}

  4. 4. Where does the file live?

    Claude Code reads .mcp.json from your project root (or ~/.claude.json globally). For Claude Desktop / Cursor / Cline, paste the same JSON into the client's MCP config dialog.

  5. 5. Restart your AI client

    Claude Code, Cursor, etc. pick up MCP servers on restart. You'll see the mcptask-online server listed in available tools.

info

Other MCP clients

Standard MCP over SSE. Use the same URL (https://mcptask.online/mcp/sse) and the same Authorization: Bearer header as above.

downloadPrefer a one-shot installer? See the /installation page for a guided setup on macOS, Linux, and any system.

Available MCP Tools

The 12 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
create_pieceCreate a new piece (task, story, epic, recurent)
get_pieceFetch a single piece by ID
list_piecesList pieces with filters (project, status, type)
get_next_taskGet the highest-priority available task
get_project_treeGet the project hierarchy (epics/stories/tasks)
list_projectsList projects you have access to
get_projectFetch one project's metadata
get_current_userIdentify the user behind the current token
log_work_progressLog effort on a piece and update its progress
add_messageAdd a comment / message to a piece
add_attachmentAttach a file to a piece
get_piece_effortsRead time-tracking entries for a piece
get_usage_guideSelf-describe the server (capabilities and usage hints)

Authentication

One credential, one env var. No API key dashboard, no OAuth app to register.

MCPTASK_TOKEN (Bearer):

  • vpn_keyGenerate from Settings → API Access in mcptask.online
  • vpn_keyTied to your user account, scoped to your workspaces
  • vpn_keyRevoke or rotate anytime from the same page
  • vpn_keyTreat it like a password — anyone holding it acts as you

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

Rate Limits

PlanRequests/Hour
Starter1,000 requests/hour
Professional10,000 requests/hour
EnterpriseCustom

These numbers are realistic but not yet enforced by a hard limiter — they describe the target SLA. Contact us if you hit a wall.

Version Control (Inbound Webhooks)

These are inbound webhooks — your Git host calls mcptask.online when something happens. Outbound webhooks (mcptask.online → your systems) are planned, see below.

GitHub Integration

check_circleLive (Inbound Webhooks)schedule5 minutes

Features

codeWebhook-based event processing (push, pull request)
codePull request body parsed for piece references (e.g. #Task-47)
codePR opened/merged linked to the matching piece as a comment
codeTime logged from PR merge when a duration is included

How it works

  1. 1Open the piece in mcptask.online and copy its webhook URL — every piece has a unique URL like https://mcptask.online/github/efforts/<token>
  2. 2Add that URL as a webhook in your GitHub repository (Settings → Webhooks)
  3. 3Select events: Push, Pull request
  4. 4Save the webhook (no secret required)
  5. 5Reference the piece in commits and PR bodies: e.g. "Fix login #Task-47 2h"
  6. 6mcptask.online receives the webhook, links the PR, and logs time

Where do #Task-47 references come from?

mcptask.online's piece relative IDs (e.g. 47) become the reference token #Task-47. You'll find them on every piece page and in the URL — the public mcptask://pieces/{account_code}/{piece_id} URI form is the canonical handle.

Examples:

 Fix login #Task-47 2hImplement OAuth #Story-48 3h 30mRefactor auth #Epic-49 (no time logged, just a link)

Pull Request Integration

  • mergePR title/body parsed for piece references (any #Task-N, #Story-N, #Epic-N, #Recurent-N)
  • mergePR opened → comment added on the piece with PR link
  • mergePR merged → last open effort is closed, PR comment updated
  • mergePR status visible on the piece timeline

Configuration Options

settingsMultiple repositories per project
settingsPrivate repository support (works with any GitHub repo the webhook can reach)
settingsCustom piece reference patterns (default: #Task-N, #Story-N, #Epic-N, #Recurent-N)
settingsBranch-based status updates

GitLab Integration

check_circleLive (Inbound Webhooks)schedule5 minutes

Features

codeSame capabilities as GitHub (push, merge request)
codeWorks with GitLab.com (SaaS)
codeWorks with self-hosted GitLab (12.0+)
codeMerge request linking

Self-Hosted Setup

  1. 1Copy the piece's webhook URL from mcptask.online (same shape as GitHub: /gitlab/efforts/<token>)
  2. 2Add the URL as a webhook in your GitLab project (Settings → Webhooks)
  3. 3Trigger: Push events, Merge request events
  4. 4Test the webhook delivery from GitLab UI

Security

securityWebhook signature verification
securityToken-based authentication (per-piece URL token)
securityNo source code access (metadata only)
securityTLS encryption required

Project Management Import

Jira Import

scienceBeta (Import on Request)workspace_premiumProfessional, Enterprise

What imports

checkIssue hierarchy (Epic > Story > Task > Subtask)
checkDescriptions and basic acceptance criteria
checkComments and discussions
checkFile attachments
checkTime logs (worklogs)

What doesn't import

removeJira workflows (mcptask.online uses simpler states)
removeJira plugins/extensions
removeAdmin settings and permission schemes
removeSprint history (we map to current state only)
removeCustom field mapping UI (we take a best-effort pass)

Process

  1. 1Contact us with your Jira instance URL and a read-only API token
  2. 2We run the import together (background job, manual kickoff)
  3. 3You review the field mapping and approve
  4. 4We re-run if anything looks off
scheduleTypical time: depends on project size — usually a half-day with our help

Trello Import

scienceBeta (Import on Request)workspace_premiumProfessional, Enterprise

What imports

checkBoards → Projects
checkLists → Epics or states (configurable)
checkCards → Tasks
checkChecklists → Subtasks
checkAttachments
checkComments
checkLabels → Tags
checkDue dates

Mapping Options

arrow_forward
HierarchicalLists become Epics containing tasks
arrow_forward
FlatLists become task states
arrow_forward
CustomDefine your own mapping

Process

  1. 1Authorize Trello access from Settings → Integrations
  2. 2We pick the boards to import and the mapping style together
  3. 3Start the import
  4. 4Review and adjust
scheduleTypical time: 10-30 minutes with our help

EasyRedmine Import

support_agentAvailable on RequestdiamondEnterprise

Contact us for EasyRedmine migration assistance.

Enterprise Migration Support

Our team will help you migrate from EasyRedmine with minimal downtime.

mailContact Sales

Invoicing & Billing

Fakturoid (Czech Republic)

check_circleLiveverifiedAll Plans

Features

checkOAuth 2.0 authentication
checkExport approved efforts → Invoices
checkAutomatic VAT calculation (CZ rates)
checkClient mapping (Fakturoid contact ↔ mcptask.online company)
checkPayment tracking

Workflow

  1. 1Approve efforts in mcptask.online
  2. 2Click "Export to Fakturoid"
  3. 3Invoice created in Fakturoid
  4. 4Review and send from Fakturoid
  5. 5Mark as billed in mcptask.online
scheduleSetup Time: 5 minutes

iDoklad (Czech Republic)

check_circleLiveverifiedAll Plans

Features

checkOAuth 2.0 authentication
checkInvoice generation
checkVAT compliance (CZ)
checkMulti-currency support
checkBank statement matching (manual today; full sync is on the roadmap)

Workflow

Same shape as Fakturoid — select efforts, export, invoice. iDoklad's bank sync is read-only on our side today; full reconciliation is planned.

Stripe (mcptask.online's Own Billing)

check_circleLivecredit_cardAll Plans
info

Heads-up: Stripe here powers mcptask.online's own subscription billing (per-seat Starter/Professional/Enterprise). It is NOT a way to bill your clients through mcptask.online. For client billing, use Fakturoid or iDoklad above.

What Stripe does here

checkCharges your card for the mcptask.online plan you chose
checkPer-seat subscription, prorated on add/remove
checkFailed payment handling (we email + retry, then downgrade)
checkInvoice PDFs from Stripe for your accounting
checkMulti-currency for international cards

This is for…

arrow_forwardPaying mcptask.online for your team's seats
arrow_forwardGetting a clean Stripe-issued invoice for your expense report
arrow_forwardUpgrading/downgrading plans without contacting us

REST API

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

checkMCPTASK_TOKEN as Bearer header (same token as MCP)
checkPer-request signature header (X-MCPTASK-Signature) for higher-security flows

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/v1/{account_code}/projects - List projects
codeGET /api/v1/{account_code}/projects/{id} - Get project
codePOST /api/v1/{account_code}/projects - Create project
codePUT /api/v1/{account_code}/projects/{id} - Update project
Pieces (Tasks, Stories, Epics, Recurents)
codeGET /api/v1/{account_code}/pieces - List pieces
codeGET /api/v1/{account_code}/pieces/{id} - Get piece
codePOST /api/v1/{account_code}/pieces - Create piece
codePUT /api/v1/{account_code}/pieces/{id} - Update piece
Efforts
codeGET /api/v1/{account_code}/pieces/{id}/efforts - List efforts
codePOST /api/v1/{account_code}/pieces/{id}/efforts - Log effort
Users
codeGET /api/v1/{account_code}/users - List users
codeGET /api/v1/user - Current user

Rate Limits

Same envelope as the MCP server:

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

Documentation

descriptionEndpoint reference at /api/docs (rendered OpenAPI)
descriptionCode examples in curl, Ruby, and JavaScript
descriptionLive "try it" panel that hits your account with your token

Outgoing Webhooks (Planned)

hourglass_emptyComing soon

Outgoing Webhooks (Planned)

workspace_premiumProfessional, Enterprise (planned)

Outgoing webhooks (mcptask.online → your systems) are on the roadmap. They do not exist today — vote for them on the Roadmap section below to help us prioritize.

Events planned for v1

This is the shape we have in mind. Nothing here is live yet.

hourglass_emptypiece.created
hourglass_emptypiece.updated
hourglass_emptypiece.completed
hourglass_emptyeffort.logged
hourglass_emptycomment.added
hourglass_emptysprint.started
hourglass_emptysprint.completed

Use cases we have in mind

checkSend Slack/Teams notifications
checkTrigger CI/CD pipelines on piece transitions
checkUpdate external dashboards
checkCustom automation in Zapier / n8n / Make

How it will work (planned)

  1. 1Add a webhook URL in Settings → Integrations → Outgoing webhooks
  2. 2Select which event types to send
  3. 3Configure a secret for HMAC signature verification
  4. 4Send a test event from the UI
  5. 5We retry with exponential backoff on non-2xx responses
info

Need something today?

The fastest way to react to mcptask.online events today is to read them via MCP or the REST API from a small script. Or wire a GitHub/GitLab outbound webhook from your repo (if the trigger is in your repo) — those are live now.

Requested Integrations (Roadmap)

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

chat

Communication

thumb_up
Slack — task notifications and slash commands
thumb_up
Microsoft Teams — same shape as Slack
thumb_up
Discord — for dev teams running on Discord
calendar_month

Calendar

thumb_up
Google Calendar — sync piece deadlines
thumb_up
Outlook — Microsoft ecosystem
design_services

Design

thumb_up
Figma — link design frames to pieces
cloud_upload

Cloud Storage

thumb_up
Google Drive — attach files from Drive
thumb_up
Dropbox — file integration

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

Integration Comparison by Plan

IntegrationStarterProfessionalEnterprise
MCP Servercheck_circlecheck_circle✓ (dedicated)
GitHub (Inbound Webhook)check_circlecheck_circlecheck_circle
GitLab (Inbound Webhook)check_circlecheck_circlecheck_circle
Fakturoidcheck_circlecheck_circlecheck_circle
iDokladcheck_circlecheck_circlecheck_circle
Stripe (mcptask billing)check_circlecheck_circlecheck_circle
Jira Import—BetaBeta
Trello Import—BetaBeta
REST API—check_circlecheck_circle
Outgoing Webhooks—PlannedPlanned
Custom Integrations——check_circle

Connect Your Workflow Today

arrow_forward
Start Free TrialMCP server and Git integrations included
descriptionView API Docs

Need custom integration or migration assistance?

support_agentRequest Custom Integration