Telos MCP Server

Telos MCP server exists for a simple reason — assistants are far more useful when they can act on Telos directly instead of describing what you should do. Task planning MCP server with markdown file storage.

What you get

Task planning and tracking for AI agents. An MCP server with project-based organization and Obsidian-compatible markdown storage.

• Create, update, list, delete — tasks with full status tracking
• Projects — — organize tasks by project with metadata (tech stack, repo URL, sources)
• Dependencies — — blockedBy/blocks relationships between tasks
• Bulk operations — — create multiple tasks at once
• Task tree — — hierarchical view of tasks with parent-child relationships
• Markdown files — — each task is a folder with README.md and YAML frontmatter

Setting it up

The server ships on npm as telos-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need one environment variable: TELOS_DIR. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the telos mcp server does with a few real requests.

Choosing this one

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by skye-flyhigh; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Telos's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.