The callback already verifies state β reusing it for Google loginβ¦
- Editapp/models/user.rb2.1sWire provider column into auth flow
mcptask.online - hand off a well-defined task in the evening, wake up to a merged PR and draft invoices. Your AI agents run on your machines against your real tests, on premium or cheap models - you pick.
For example, four runners, four different models - including cheap ones. They run on your machines against your real environment, not inside someone else's sandbox.
Sample view of a live runner activity dashboardThe callback already verifies state β reusing it for Google loginβ¦
When a runner hits a failing test in code it was not asked to touch, it files its own tracked Bug task, branches off, fixes it, merges, and comes back. Nobody else ships that loop end-to-end.
Use cases written for the person signing the invoice - not the person writing the code
You have a backlog that won't shrink. The agents pick up the well-defined tasks overnight, log their work, and open PRs. Your team reviews in the morning instead of typing.
Premium model APIs eat your runway. mcptask.online is model-agnostic - the same agent harness runs Claude, GPT, or cheap open-weights models. Pay for what closes the task, not for the brand.
Hand off a well-defined task before you leave. Agents work overnight against your real tests. You wake up to a merged PR, a work log, and a draft invoice. No copy-paste of context the next morning.
Manage projects from Claude Cowork, Claude Desktop, or any MCP client. Ask for a status, create a task, log a meeting - all from chat. The agents work from the same queue.
AI coding tools are powerful, but they can't see your task system
Every time you start with Claude Code or Copilot, you manually paste the task description, acceptance criteria, and context. Over and over. For every task.
Your AI assistant helped fix 5 bugs today. But your task system shows nothing. You spend 30 minutes reconstructing what was done and logging it manually.
You want AI to work through your backlog automatically. But it can't see the queue, can't prioritize, can't move to the next task when done.
Your manager asks: 'What exactly did the AI do on this feature?' You have no structured answer. Chat logs are scattered. Nothing is documented.
mcptask.online provides a dedicated MCP server that AI agents speak natively
One command (`bundle exec rake mcptask_runner:install`) provisions the MCP connection, Claude Code skills, baseline permissions, and your access token. On macOS it also offers a weekday 08:00 scheduler. `rake mcptask_runner:update` keeps skills current without overwriting local tweaks. Seniors stop wrestling with `.mcp.json` and token plumbing.
Our MCP (Model Context Protocol) server lets AI assistants like Claude Code read tasks, understand context, and log work - using the same protocol they speak natively. No scraping. No fragile APIs. Clean, structured communication.
One command (`bundle exec rake mcptask_runner:install`) provisions the MCP connection, Claude Code skills, baseline permissions, and your token. Then the AI agent fetches the next highest-priority task, completes the work, logs progress, and moves on. Human oversight when needed. Full automation when appropriate.
Connect repositories via webhooks. Commits automatically log time. Pull requests link to tasks. Merges update status. On the Professional plan, the same data flows straight into Fakturoid or iDoklad as a draft invoice. No other tool covers the whole loop, from a task to a paid invoice.
Task -> Agent work -> PR -> Merge -> Timesheet -> Draft invoice in Fakturoid / iDoklad
Humans use the elegant web interface. AI uses the MCP server. Both see the same tasks, same progress, same history. Complete transparency.
Organize work the way it actually happens. Large features break into stories. Stories break into tasks. Tasks can have subtasks. AI and humans navigate the same structure.
Every action is logged: task created by human, picked up by AI, progress logged, status changed, completed. Full attribution. Full history. Full accountability.
Create your account, reserve a machine for the agent, add the agent as a user, then run one install command
After setup, the agent works autonomously. You review completed work and steer priorities.
If you only need a task-aware assistant in Claude Code or any MCP client, connect manually with this tiny `.mcp.json` snippet.
{
"mcpServers": {
"mcptask-online": {
"type": "sse",
"url": "https://mcptask.online/mcp/sse",
"headers": {
"Authorization": "Bearer ${MCPTASK_TOKEN}"
}
}
}
}This is the lighter path β no runner, no autonomous PRs.
Start free. Upgrade when your AI does more work than you expected.
Prices exclude VAT (+ VAT where applicable)
Min. 2
Solo developers using AI assistants
Prices exclude VAT (+ VAT where applicable)
Min. 5
Teams using AI-assisted development
Min. 200
Organizations running multiple AI agents at scale
"Finally, my Claude Code sessions have full context. It reads the task, understands the requirements, and logs its work automatically. No more copy-paste ceremonies."
"We run 3 coding agents overnight. mcptask.online is their task queue. Every morning we review what they completed. Full transparency, zero manual logging."
"The GitHub webhook integration means I never log time manually. Commit message includes task reference, time is logged automatically. AI or human, doesn't matter."
"Switched from Jira. Setup took 30 minutes instead of 3 days. Now we're ready for AI assistants when we adopt them. Already cleaner than Jira was."
Four things other AI coding tools don't have. First, model-agnostic: the same harness runs Claude, GPT, or any open-weights model - including cheap ones - so you never get locked into a premium API bill. Second, runs on your infrastructure against your real database and your real tests, not inside someone else's sandbox. Third, the only tool that covers the whole lifecycle, from a task in the backlog to a draft invoice in Fakturoid or iDoklad. Fourth, zero-config setup: one command provisions the MCP connection, skills, permissions, and token, while rivals leave your senior staff wiring agent configuration by hand.
MCP (Model Context Protocol) is the standard protocol that AI assistants like Claude use to communicate with external tools. mcptask.online provides a dedicated MCP server, meaning AI can read your tasks, update status, and log work using its native language - not through fragile web scraping or custom APIs. You don't build the connection manually - the runner provisions it during install.
Any AI assistant that supports MCP protocol: Claude Code, Claude Desktop, and other MCP-enabled tools. The MCP server provides read and write access to tasks, efforts, and project data.
Yes! Configure your AI to fetch the next highest-priority task, complete it, log progress, and move on. You set the boundaries (which projects, which task types). AI works within those boundaries.
Add our webhook to your repository. When developers (human or AI) commit code with task references (e.g., '#Task-47 2h'), mcptask.online automatically logs the time and updates the task. Pull request merges can auto-complete tasks.
Yes. All data encrypted at rest and in transit. Servers in EU data centers. GDPR compliant. Role-based access control means AI agents only see what you authorize.
Yes! Professional and Enterprise plans include import tools for Jira and Trello. Your existing tasks, hierarchy, and history come over. Then connect AI and enhance your workflow.
Practically no. `bundle exec rake mcptask_runner:install` runs the whole setup (MCP `.mcp.json`, token, skills, permissions, and a weekday scheduler on macOS) in about 2 minutes, and `rake mcptask_runner:update` keeps skills current without overwriting local tweaks.
Export all data (JSON, CSV) before canceling. We retain data 90 days in case you return. After 90 days, permanently deleted per GDPR requirements.
Yes! Each AI agent has their own user in the system. AI agents can connect to MCP unlimited times, but their actions are logged.
Yes! 30-day free trial with full features. No credit card required. Connect your AI assistant during trial.
Full EU data protection compliance
Data stored in Frankfurt, Germany
Native Model Context Protocol support
AI sees only what you authorize
Every AI action logged and traceable
SLA-backed reliability
Your data is protected by enterprise-grade security
Hand off a well-defined task tonight. Wake up to a merged PR and a draft invoice.
Trusted by AI-forward teams. GDPR compliant. EU servers. Cancel anytime.
Trusted by AI-Forward Teams
Tasks Completed by AI
AI agents using MCP server to complete work
Hours Logged
Automatically and manually tracked
MCP Server Uptime
AI agents always connected
Command to install
On a machine with your project and Claude Code ready