sync-task-schemaLABSCO SUMMARY
A task list that lives in your database, not in someone's SaaS.
Directus supplies the storage, the admin UI and the permissions; this puts a conversational front end on top, and one tool call, sync-task-schema, creates the Task collection in your database before the first write.
What it is
An MCP server for a task collection in Directus. It talks to a Directus instance over its API, validates every write against Zod schemas, and can create the collection itself rather than asking you to click it together.
What you get
- The Task schema synchronised into your Directus database, so the collection exists before the first write
- All tasks listed, with filtering by status and priority and a result limit
- A single task read by ID
- Tasks created, updated and deleted
- The identity the server is currently authenticating as
Requirements
Node.js 18 or newer and a Directus instance you control. Authenticate with DIRECTUS_TOKEN, or with a Directus account's email and password instead. The README's sample config ships a working URL and token for the author's own instance — replace both with yours before you connect, or your tasks land in somebody else's database.
Setup effort
Build from source — git clone https://github.com/creatuluw/tpl.mcp-server.git
USE CASES
01
Starting from an empty Directus
Push the Task schema into the database so the collection and its fields exist before anything is written.
02
Seeing what is open right now
List tasks filtered by status and priority, capped at a number you can actually read.
03
Capturing work as it comes up
Create the task in the middle of the conversation that produced it.
04
Moving a ticket along
Read the task by ID, then write the status change back.
05
Clearing out what no longer applies
Find it in the list, confirm it is the right one, then delete it.
06
Checking which account you are connected as
Read back the identity the token resolves to before making writes against a shared instance.
7 tools
Listed in project docs. Your client may show a different list.
list-tasksget-taskcreate-taskupdate-taskdelete-taskget-user-infoBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- node on PATH
- Node.js 18+
- A Directus instance you control
- DIRECTUS_URL and DIRECTUS_TOKEN — or DIRECTUS_USER_EMAIL and DIRECTUS_USER_PASSWORD instead of the token
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/creatuluw/tpl.mcp-server.git
cd tpl.mcp-server
npm install
npm run buildMCP Clients
Cursor, Claude Desktop
JSON
{
"mcpServers": {
"directus-tasks": {
"command": "node",
"args": [
"<YOUR_PATH_TO_TPL_MCP_SERVER>/dist/index.js"
],
"env": {
"DIRECTUS_URL": "<YOUR_DIRECTUS_URL>",
"DIRECTUS_TOKEN": "<YOUR_DIRECTUS_TOKEN>"
}
}
}
}<YOUR_PATH_TO_TPL_MCP_SERVER> is the absolute path of your clone, and <YOUR_DIRECTUS_URL> is your own Directus instance's URL, and <YOUR_DIRECTUS_TOKEN> is an API token from it (or set DIRECTUS_USER_EMAIL and DIRECTUS_USER_PASSWORD instead of the token). Do not leave them out: the server falls back to the author's own instance and token.
