LTD MCP

What the LTD MCP MCP server does

The LTD MCP MCP server gives AI agents an MCP interface to an LTD workspace. It covers project visibility, task lookup, task management, comments, project-health summaries, and analytics. Agents can inspect the projects available to their token, review project configuration, search or retrieve tasks, and list their own open work.

Write access includes task creation, task updates, assignment changes, and comments. These operations are separated from read access through API-token scopes, so a token can be limited to project visibility or granted permission to make changes.

How it works

The service is hosted at https://api.eshway.com/mcp/ and uses Streamable HTTP. Clients send a bearer token in the Authorization header. The token determines which LTD projects and operations the agent can access.

Writes use a two-stage process. A preview request returns the proposed change and a short-lived confirmation token without modifying LTD. The agent must then submit the same arguments with mode="confirm" and the returned token. Confirmation tokens are single-use, and preview responses state that nothing has changed yet. Invalid assignees and statuses are rejected before a write is performed.

Setup and configuration

Create an LTD API token in LTD Settings under API tokens. Use mcp:read for read-only access. Add mcp:write when the agent must create tasks, update tasks, assign owners, or add comments. Keep the token secret, and revoke or rotate it from LTD settings when necessary.

A generic MCP HTTP configuration points the client to the hosted endpoint and supplies the token through an environment variable:

{
  "mcpServers": {
    "ltd": {
      "transport": "http",
      "url": "https://api.eshway.com/mcp/",
      "headers": {
        "Authorization": "Bearer ${LTD_API_TOKEN}"
      }
    }
  }
}

Hermes can add the server with its HTTP transport command. Smithery can register the same endpoint with smithery mcp add. The repository also identifies Claude Desktop, Cursor, Cline, and Windsurf as planned client-specific documentation targets; any client that supports remote HTTP or Streamable HTTP MCP servers should be able to connect.

Tools and capabilities

Read tools include:

• ltd_list_projects for accessible projects
• ltd_describe_project for statuses, custom fields, and members
• ltd_search_tasks and ltd_get_task for task discovery and detail
• ltd_my_tasks for the token owner's open tasks
• ltd_get_comments for task discussions
• ltd_project_pulse for project health rollups
• ltd_analytics_query and ltd_drilldown_tasks for analytics and task-level follow-up

Write tools include ltd_create_task, ltd_update_task, and ltd_add_comment. Each write should be previewed and then confirmed explicitly.

Limitations and notes

The LTD MCP MCP server is in early public preview. Hosted documentation, a demo workspace, client-specific setup guides, OAuth support, audit-log documentation, and several registry listings are listed as roadmap items rather than current capabilities.

The repository states that its documentation and examples are MIT-licensed, while the hosted LTD service and server implementation are owned by Eshway. API-token access is required, and the available projects and actions depend on token scopes.