home / mcp / mcp task aggregator mcp server
Aggregates tasks from Jira, Markdown, and STM into a single SQLite database with MCP tools for listing and syncing tasks.
Configuration
View docs{
"mcpServers": {
"89jobrien-mcp-joecc": {
"command": "uv",
"args": [
"run",
"mcp-task-aggregator"
],
"env": {
"JIRA_URL": "https://your-domain.atlassian.net",
"LOG_LEVEL": "INFO",
"JIRA_EMAIL": "[email protected]",
"STM_ENABLED": "true",
"DATABASE_PATH": "~/.mcp-task-aggregator/tasks.db",
"JIRA_API_TOKEN": "YOUR_API_TOKEN",
"JIRA_PROJECT_KEY": "AGENTOPS",
"MARKDOWN_ENABLED": "true",
"STM_SEARCH_PATHS": ".",
"MARKDOWN_SEARCH_PATHS": "."
}
}
}
}You can run the MCP Task Aggregator server to unify tasks from Jira, Markdown, and STM sources into a single SQLite database, exposing practical MCP tools to list and sync tasks with incremental updates.
Start the MCP Task Aggregator server and connect your MCP client to access the built‑in tools. You can list tasks, filter by source or status, and trigger synchronizations from external sources. The server maintains a unified SQLite database with full‑text search and tagging, enabling efficient task discovery across multiple sources.
Prerequisites: ensure you have a compatible runtime environment installed. You will use the MCP runtime to execute the server. The following steps assume you are working on a Unix‑like system.
Step by step commands to run the server locally via the standard MCP runtime:
uv sync
# Start the MCP server
uv run mcp-task-aggregatorConfigure the server via environment variables. Copy a sample configuration file to your deployment environment and edit the values to match your setup.
Key variables you may set include:
- DATABASE_PATH: SQLite database path. Default is ~/.mcp-task-aggregator/tasks.db.
- LOG_LEVEL: Logging level (e.g., INFO).
- JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN, JIRA_PROJECT_KEY: Jira integration details.
- MARKDOWN_ENABLED, MARKDOWN_SEARCH_PATHS: Enable and locate Markdown TO‑DO parsing.
- STM_ENABLED, STM_SEARCH_PATHS: Enable and locate STM CLI synchronization.
Incremental sync is supported by detecting changes via hash comparisons to avoid reprocessing unchanged data.
The server provides MCP tools for querying and syncing data, enabling you to manage tasks efficiently across multiple sources.
Query tasks with optional filters such as source, status, priority, and tags, with pagination support.
List only local tasks as a shortcut for listing with source set to local.
Synchronize tasks from configured external sources, with options for full refresh and incremental updates.