
LTD MCP
io.github.EshllerPublished by GitHub account Eshllerv0.1.0Updated Oct 24, 2026
Project management MCP for AI agents with safe task reads and writes.
Overview
Remote MCP server that lets an AI assistant read and write project work in an LTD workspace: projects, tasks, comments and analytics.
- What you can do
- List and describe accessible projects, including statuses, custom fields and members; list the token owner's open tasks and read task comments and full task detail; search and filter tasks; get project health rollups and run analytics aggregations with drill-down into datapoints; create tasks, update task fields and add comments through a two-step preview-confirm flow.
- When to use it
- Use it when your team works in LTD and you want an assistant to inspect project health, find or summarize tasks, or draft and apply task changes and comments under human confirmation.
- Requirements
- A remote Streamable HTTP endpoint; no local package. An LTD API token created in LTD Settings, sent as a Bearer token in the Authorization header. Scopes mcp:read for read-only access and mcp:write for task creation, updates, assignment and comments. Network access to the endpoint.
Installation
In SourceWeft
- Open LTD MCP in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Eshller%2Fltd-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"ltd": {
"type": "http",
"url": "https://api.eshway.com/mcp/",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
LTD MCP
Project management MCP for AI agents.
LTD MCP lets AI agents connect to an LTD workspace over MCP and safely operate project work: inspect project health, search tasks, create tasks, update tasks, assign owners, and add comments using scoped API tokens and preview-confirm writes.
Status: early public preview. Read tools are available. Write tools use a two-step preview-confirm safety flow.
Why this exists
Most project management tools were built for humans clicking dashboards. AI agents need safe, structured tools.
LTD MCP is the agent-native interface for LTD, an anti-Jira-style project workspace for teams that want humans and AI agents operating together.
MCP endpoint
Transport: Streamable HTTP / HTTP MCP
Authentication: Bearer token
Capabilities
Read tools
ltd_list_projects- list projects the token can accessltd_describe_project- describe statuses, custom fields, and membersltd_search_tasks- search/filter tasksltd_get_task- fetch full task detailltd_my_tasks- list token owner's open tasksltd_get_comments- read task commentsltd_project_pulse- project health rollupsltd_analytics_query- analytics aggregationsltd_drilldown_tasks- drill into analytics datapoints
Write tools
ltd_create_task- create a taskltd_update_task- update fields on a taskltd_add_comment- add a comment
Write tools are intentionally two-step:
mode="preview"returns the exact proposed change and a short-lived confirm token. Nothing is written.mode="confirm"with the same arguments plusconfirm_tokenperforms the write.
Token scopes
Create an LTD API token from LTD Settings → API tokens.
Recommended scopes:
mcp:readfor read-only project visibilitymcp:writefor task creation, updates, assignment, and comments
Keep tokens secret. Revoke and rotate them from LTD settings when needed.
Quickstart
Generic MCP HTTP config
Hermes
Smithery
Example prompts
Safety model
LTD MCP is designed for human-controlled agent operations:
- Scoped PATs limit access.
- Read and write scopes are separate.
- Write actions use preview-confirm.
- Preview explicitly returns
nothing_changed_yet: true. - Confirm tokens are short-lived and single-use.
- Invalid assignees/statuses are rejected before write.
Example write flow
Preview:
Confirm:
Supported clients
Any MCP client that supports remote HTTP / Streamable HTTP MCP servers should work.
Planned docs:
- Claude Desktop
- Cursor
- Cline
- Windsurf
- Hermes / ZERO
- Smithery
Links
- MCP endpoint: https://api.eshway.com/mcp/
- Website: https://ltd.eshway.com/
- Product: LTD by Eshway
Roadmap
- Public hosted docs
- Demo workspace
- Client-specific setup guides
- Official MCP Registry listing
- Smithery listing
- MCP.so listing
- Audit log docs
- OAuth support
License
MIT for documentation and examples in this repository. LTD server implementation and hosted service are owned by Eshway.
Source: README.md at commit bb04aad
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts