mcptask.online
Autonomous AI developers on your own infrastructure – as many as you need.
What it can do
- UpdatePieceTool: Update the mutable attributes of an existing Task, Story, Epic or Recurent by relative_id. Only the attributes passed are changed; omitted ones are left alone. Returns before/after fo
- SendOutreachEmailTool: Send a personalized outreach email (plain text preferred) from your own address through the outreach pipeline. Rate limited to 3/day, refuses suppressed and already-contacted (d
- ManageBlockerLinksTool: Add or remove blocked_by links on a piece. Batch operation: one bad id rejects the whole call.
What data it sees
Do you need an account
No: the server works without sign-in
Autonomous AI developers on your own infrastructure – as many as you need.
Assign a task; the runner (Claude Code, Codex, OpenCode) on your machine works against your repo and tests and delivers a pull request to GitHub, GitLab or Bitbucket. Any model, premium or cheap – your data stays with you. Your people keep the complex work, AI developers take the rest. Work is logged into timesheets and invoice inputs.
- Endpoint:
https://mcptask.online/mcp(Streamable HTTP, OAuth / Bearer token) - Runner install & docs: https://mcptask.online/installation?language=en
- Runner releases: https://github.com/jchsoft/mcptask-releases
Example prompts: "Get my next task from mcptask and start working on it." · "Create a Story with two tasks and make the second wait for the first." · "Log 50 % progress on task #12495." · "Export this month's timesheet for project 7 as CSV."
How to connect
How to connect mcptask.online to Claude
The server address to paste into Claude settings:
https://mcptask--chmel.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect mcptask.online to ChatGPT
The server address to paste into ChatGPT settings:
https://mcptask--chmel.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect mcptask.online to Cursor
The server address to paste into Cursor settings:
https://mcptask--chmel.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (21)
Raw names from tools/list. Only developers need these.
| UpdatePieceTool | Update the mutable attributes of an existing Task, Story, Epic or Recurent by relative_id. Only the attributes passed are changed; omitted ones are left alone. Returns before/after for each attribute touched. A dependency on another piece is declared with blocked_by_relative_ids — the updated piece waits for the ids listed there. Removing a link is not done here: use ManageBlockerLinksTool, where piece_relative_id is the WAITING piece and blocker_relative_ids are the pieces it waits for. |
| SendOutreachEmailTool | Send a personalized outreach email (plain text preferred) from your own address through the outreach pipeline. Rate limited to 3/day, refuses suppressed and already-contacted (dedupe_key) recipients. |
| ManageBlockerLinksTool | Add or remove blocked_by links on a piece. Batch operation: one bad id rejects the whole call. |
| LogWorkProgressTool | Log work progress performed by the agent with automatic task state management |
| ListTimeSheetReportOptionsTool | Lists available filters for the timesheet report: date range, companies, projects, workers and report layout options. Values are scoped to the authenticated user's role. |
| ListProjectsTool | List the current user's projects under an account. |
| ListPiecesTool | Paginated list of doable pieces (Tasks, Stories, Recurents) for an account. Start with size 10; use size 5 for large pieces. |
| GetUsageGuideTool | The McpTask.online usage guide (how to use this MCP server) as markdown. |
| GetProjectTreeTool | Hierarchical tree of a project (Root -> Epic -> Story terminal). Compact nodes: id, kind, type, children_count, shortened name. |
| GetProjectTool | Extended project information by relative ID: options, users with roles, and task summary. |
| GetPieceTool | Read comprehensive details of a single piece (Task/Story/Epic/Recurent) by its relative ID, including subtasks, messages and attachments. |
| GetPieceEffortsTool | Effort (time tracking) history for a piece by its relative ID (most recent 50 entries). |
| GetNextTaskTool | Get the next task or story to work on (highest priority, errors first, oldest within priority). Optionally filter by project. If you are waiting on something for a piece (a human answer, a review, a deploy) and have not formally blocked it, pass its relative id in exclude_relative_ids to skip it and get the next unblocked piece instead of looping on the same one. |
| GetCurrentUserTool | Current authenticated user: profile, accessible account codes, today's working hours (hour_goal, work_start, worked_out), and respect_working_hours flag (per Company role, see task #11687). |
| GetAttachmentTool | Attachment metadata and a direct download URL for a piece attachment (avoids inlining binary content). |
| GetAccountTool | Account workspace details by account code: attributes, account-level users, permitted projects, and permitted companies. |
| ExportTimeSheetReportTool | Exports a timesheet report in JSON, CSV or PDF. Filters (companies, projects, workers, date range) are scoped to the authenticated user's role. |
| CreatePieceTool | Create new work items (Tasks, Stories, Epics, Recurents) in McpTask.online with full authorization controls. A dependency on another piece is declared with blocked_by_relative_ids — the new piece waits for the ids listed there. Existing links are managed with ManageBlockerLinksTool, where piece_relative_id is the WAITING piece and blocker_relative_ids are the pieces it waits for. |
| BlockTaskTool | Block or unblock a task that cannot be completed temporarily |
| AddMessageTool | Add a note/message to a task with optional file attachment |
| AddAttachmentTool | Upload a file attachment directly to an existing task/story/piece |