AgentTasker MCP Server
A lightweight stdio-only MCP server that allows AI agents to run multiple tasks (e.g., Python code, HTTP requests, shell commands) in parallel or with dependencies, returning structured results in a single call.
README
AgentTasker MCP Server
<!-- mcp-name: io.github.S3bRR/agent-tasker-mcp -->
AgentTasker is a small, stdio-only MCP server for AI agents that need to run multiple tasks quickly and get structured results back in one call.
It is intentionally narrow:
- two tools:
executeandexecute_batch - local stdio transport only
- zero third-party runtime dependencies
- explicit dependency control with
depends_on - compact, model-friendly JSON responses
Repository: https://github.com/S3bRR/agent-tasker-mcp
Why This Exists
Most agent orchestration layers are heavier than they need to be. This project is designed for the common case:
- run a few tasks in parallel
- let one task wait on another when needed
- keep the MCP surface small enough for models to use reliably
There is no queue service, no persistence layer, no background worker system, and no SDK dependency required at runtime.
What It Supports
Task types:
python_codehttp_requestdiscovery_searchweb_scrapeshell_commandfile_readfile_write
Public MCP tools:
executeexecute_batch
Install
Requirements:
- Python 3.10+
- A local MCP client that can run stdio servers
Recommended: uvx
Run directly from GitHub:
uvx --from git+https://github.com/S3bRR/agent-tasker-mcp.git agent-tasker-mcp-server --workers 8
Once the package is live on PyPI, the command becomes:
uvx agent-tasker-mcp-server --workers 8
pipx
Install directly from GitHub:
pipx install git+https://github.com/S3bRR/agent-tasker-mcp.git
Once the package is live on PyPI, the command becomes:
pipx install agent-tasker-mcp-server
Local clone
git clone https://github.com/S3bRR/agent-tasker-mcp.git
cd agent-tasker-mcp
./setup.sh
setup.sh creates a local .venv, installs this package into it, and prints an
absolute MCP config snippet. If python3 -m venv is not available, it falls back
to virtualenv when installed.
MCP Client Configuration
GitHub Source
{
"command": "uvx",
"args": [
"--from",
"git+https://github.com/S3bRR/agent-tasker-mcp.git",
"agent-tasker-mcp-server",
"--workers",
"8"
]
}
Installed Package
{
"command": "agent-tasker-mcp-server",
"args": ["--workers", "8"]
}
Local checkout
{
"command": "/absolute/path/to/agent-tasker-mcp/.venv/bin/agent-tasker-mcp-server",
"args": ["--workers", "8"]
}
Use the exact absolute path printed by ./setup.sh for local checkouts.
Usage
execute
Run one task immediately.
{
"task_type": "python_code",
"code": "result = 6 * 7"
}
execute_batch
Run multiple tasks concurrently.
{
"tasks": [
{
"name": "fetch_users",
"task_type": "http_request",
"url": "https://api.example.com/users"
},
{
"name": "calc",
"task_type": "python_code",
"code": "result = 6 * 7"
}
],
"output_mode": "compact"
}
depends_on
If one task must wait for another, make it explicit.
{
"tasks": [
{
"name": "write_file",
"task_type": "file_write",
"path": "/tmp/example.txt",
"content": "hello"
},
{
"name": "read_file",
"task_type": "file_read",
"path": "/tmp/example.txt",
"depends_on": ["write_file"]
}
]
}
If an upstream dependency fails, downstream tasks are marked failed and do not run.
Output Shape
output_mode supports:
compact(default)full
The response is ordered to match the input task list, which makes it easier for models to consume without extra reconciliation logic.
Release Process
Releases are tag-driven.
- update
pyproject.tomlandserver.jsonto the same version - commit and push to
main - create and push a matching tag such as
v1.0.0 - GitHub Actions runs tests, builds the package, publishes to PyPI through Trusted Publishing, and then publishes
server.jsonto the MCP Registry
The release workflow rejects version drift: the pushed tag, pyproject.toml, and server.json must match exactly.
Limits
Optional environment variables:
AGENT_TASKER_MAX_TASKS: maximum tasks perexecute_batchAGENT_TASKER_MAX_PAYLOAD_BYTES: maximum payload size per taskAGENT_TASKER_MAX_MEMORY_MB: soft process memory guard
Security Notes
This server is intended for trusted environments.
python_codeexecutes Python codeshell_commandexecutes shell commandsfile_readandfile_writeoperate on the local filesystem
Do not expose this server directly to untrusted users.
Development
Create a local environment:
./setup.sh
source .venv/bin/activate
Run the server:
agent-tasker-mcp-server --workers 4
Run tests:
.venv/bin/python -m unittest discover -s tests
Packaging
This repo includes server.json for MCP Registry publication and a GitHub Actions workflow that publishes both the PyPI package and MCP metadata from a version tag.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。