Agent Task List MCP Server
Provides tools to create and manage tasks organized under Linear tickets, allowing AI agents to track work items across projects. Currently tickets are entered manually, with automatic Linear sync planned for the future.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Agent Task List MCP ServerList my open tasks for the Website Redesign project."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Agent Task List
A self-hosted work queue shared by Codex, Claude Code, Claude Desktop, and any other AI client that supports the Model Context Protocol (MCP).
Project
└── Linear ticket
└── TaskEvery agent uses the same MCP tools and SQLite database. The browser UI reads and writes those records through a localhost-only API.
Why MCP
MCP is an open protocol for connecting AI applications to tools and data. Its standard transports include stdio and Streamable HTTP; clients are encouraged to support stdio for local integrations. This project uses stdio, where each AI client launches a lightweight MCP process and all processes share one WAL-mode SQLite database.
This works without tying the task list to a specific model vendor.
Related MCP server: bot-relay-mcp
Architecture
Codex ─────────────┐
Claude Code ───────┤
Claude Desktop ────┼─ stdio MCP processes ─┐
Other MCP clients ─┘ │
▼
shared SQLite DB
▲
Browser UI ───── localhost API ─────────────┘Database:
~/.local/share/agent-task-list/tasks.sqlite3Local API:
http://127.0.0.1:4783Dashboard:
http://localhost:3000
Requirements
Python 3.10 or newer
Node.js 22.13 or newer for the dashboard
An MCP-compatible AI client
Run the dashboard
Clone the repository and enter the project directory:
git clone https://github.com/vigneshr-07/agent-task-list.git
cd agent-task-listInstall the frontend dependencies once:
npm installStart the API and UI together:
npm run localOpen http://localhost:3000. The MCP server does not require the dashboard to be running; agents can update SQLite directly whenever their client launches the stdio process.
Connect Codex
Register the server in the global Codex configuration:
codex mcp add agent-task-list -- python3 /absolute/path/to/agent-task-list/tasklist.py mcpReplace /absolute/path/to/agent-task-list with the location where you cloned the repository.
Verify it:
codex mcp get agent-task-listNew Codex CLI, IDE, and desktop sessions load the global MCP registration. Reload MCP servers or restart an existing session if the tools are not visible.
Connect Claude Code
Register it at user scope so every Claude Code project and its agents can access the same task list:
claude mcp add --scope user agent-task-list -- python3 /absolute/path/to/agent-task-list/tasklist.py mcpVerify it:
claude mcp get agent-task-listClaude Code documents user-scoped MCP servers as private, cross-project integrations. Project-scoped servers can instead be committed through .mcp.json when a team should share the configuration.
Connect Claude Desktop or another MCP client
Use this standard stdio configuration:
{
"mcpServers": {
"agent-task-list": {
"command": "python3",
"args": [
"/absolute/path/to/agent-task-list/tasklist.py",
"mcp"
]
}
}
}The same configuration is available in config/mcp-stdio.example.json. Claude Desktop increasingly packages local servers as desktop extensions, but its local development MCP mode and many other desktop clients accept this standard command-and-arguments shape.
MCP tools
task_boardcreate_projectcreate_ticketcreate_tasklist_tasksclaim_taskupdate_taskupdate_ticket
Useful prompts include:
Show my open Agent Task List tasks for Website Redesign.Under project Website Redesign and ticket WEB-123, add a high-priority task to cover the retry path.Claim task 17 as claude:website-redesign:WEB-123, work on it, and mark it done after the tests pass.The intended agent workflow is:
Read board → claim task → do work → update progress → mark doneData and configuration
Override the database location when needed:
AGENT_TASK_LIST_DB=/path/to/tasks.sqlite3 python3 tasklist.py apiLOCAL_CODEX_TASKS_DB remains accepted as a compatibility fallback, but new configurations should use AGENT_TASK_LIST_DB.
To back up the board, stop active writers or use SQLite's backup command against:
~/.local/share/agent-task-list/tasks.sqlite3Development
python3 -m unittest discover -s tests/python -v
npm testBoundaries
Linear tickets are entered manually. Automatic Linear import and two-way synchronization are future work.
The API is unauthenticated because it binds only to localhost. Do not expose port 4783 to a network.
Local stdio MCP works only on the machine running the client. Cloud agents need a separately hosted, authenticated Streamable HTTP MCP service.
Task claims prevent accidental ownership changes, but this MVP does not yet provide leases or stale-claim expiry.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceA SQLite-backed message queue system that enables multiple AI agents to communicate with each other via a simple HTTP interface.Last updated4Apache 2.0
- AlicenseAqualityAmaintenanceMCP coordination primitive for multi-agent workflows. Lets multiple AI coding agents (Claude Code, Cursor, n8n, custom clients) discover each other and exchange messages and tasks via a shared SQLite-backed message bus.Last updated374953MIT
- Alicense-qualityCmaintenanceA self-hosted backlog tracker with priority scoring and an MCP server, enabling AI agents to autonomously pull, work on, and update tasks via JSON-RPC tools.Last updatedMIT
- Alicense-qualityBmaintenanceA local, project-scoped requirement management MCP server that enables AI agents to manage tasks and requirements via SQLite.Last updated11MIT
Related MCP Connectors
Local-first RAG engine with MCP server for AI agent integration.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/vigneshr-07/agent-task-list'
If you have feedback or need assistance with the MCP directory API, please join our Discord server