Windows-only headless LLM task automation engine with scheduling via Windows Task Scheduler.
Windows-only headless LLM task automation engine with scheduling via Windows Task Scheduler. That is what the assiststudio mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
After installation, the assiststudio-runner command is available globally. The published package is Windows-only because scheduling is implemented via Windows Task Scheduler and credentials are stored in Windows Credential Manager.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 7 tools. What each one is for:
create_task — Create a task with prompt, schedule, and MCP server configupdate_task — Modify task fields — partial update, only changed fieldsdelete_task — Delete a task, its executions, and log fileslist_tasks — List tasks with filtering and last execution statusrun_task — Start execution (async default, optional 60s wait)get_task_history — Query execution history with status filteringget_execution_status — Check real-time status of an executionPlenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Assiststudio's toolset — create_task, update_task, delete_task and 4 more — is a fair guide to whether it matches your workflow. It is maintained by fieldcure; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| create_task | Create a task with prompt, schedule, and MCP server config |
| update_task | Modify task fields — partial update, only changed fields |
| delete_task | Delete a task, its executions, and log files |
| list_tasks | List tasks with filtering and last execution status |
| run_task | Start execution (async default, optional 60s wait) |
| get_task_history | Query execution history with status filtering |
| get_execution_status | Check real-time status of an execution |
### From source (without dotnet tool)
```json
{
"mcpServers": {
"runner": {
"command": "dotnet",
"args": [
"run",
"--project", "C:\\path\\to\\fieldcure-assiststudio-runner\\src\\FieldCure.AssistStudio.Runner",
"--", "serve"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.