Delivery Schedule Milestones Late Report MCP server

Dated deliverables against a quote or work order. late_report says what has slipped as at any date y.

68/100?Number 1684 of 13,192 in Other

verified publishersource repositoryupdated recentlyactive entrycommand line alternative

How this score is calculated

Local VERIFIED Other

Details

Registry name
com.bestremotetools/delivery-schedule-milestones-late-report
Publisher
bestremotetools
Version
0.21.0
Distribution
Local. the server runs as a process on your own machine and talks to the client over stdio. You install the package first, and your data stays on your machine.
Transports
stdio
First published
Registry updated
Credentials required
1 environment variable
Schema generation
2025-12-11

Packages

mcpb https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/delivery-schedule.mcpb

Version
0.21.0
Transport
stdio
Runtime
not specified
Environment variables
VariableRequiredSecretPurpose
MCP_LICENSE_KEYYesYesOptional Pro license key (MCPL1....). Verified offline.

Install Delivery Schedule Milestones Late Report

Pick your client. The configuration below is generated from this server's published package and endpoint data.

Claude Code command line

Configuration file: .mcp.json or ~/.claude.json

Local package (mcpb)
claude mcp add delivery-schedule-milestones-late-report --env MCP_LICENSE_KEY=<mcp_license_key> -- https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/delivery-schedule.mcpb 

Replace each placeholder with your own value before saving.

Check it worked: Run claude mcp list and check the server reports connected.

Official Claude Code MCP documentation

Cursor IDE

Configuration file: .cursor/mcp.json or ~/.cursor/mcp.json

Local package (mcpb)
{
  "mcpServers": {
    "delivery-schedule-milestones-late-report": {
      "command": "https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/delivery-schedule.mcpb",
      "args": [],
      "env": {
        "MCP_LICENSE_KEY": "<mcp_license_key>"
      }
    }
  }
}

Replace each placeholder with your own value before saving.

Check it worked: The server appears under Settings, then MCP with a green dot.

Official Cursor MCP documentation

Claude Desktop desktop app

Configuration file: ~/Library/Application Support/Claude/claude_desktop_config.json or %APPDATA%\Claude\claude_desktop_config.json

Local package (mcpb)
{
  "mcpServers": {
    "delivery-schedule-milestones-late-report": {
      "command": "https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/delivery-schedule.mcpb",
      "args": [],
      "env": {
        "MCP_LICENSE_KEY": "<mcp_license_key>"
      }
    }
  }
}

Replace each placeholder with your own value before saving.

Quit the app completely and reopen it.

Check it worked: Look for the tools icon in the message composer.

Official Claude Desktop MCP documentation

Visual Studio Code IDE

Configuration file: .vscode/mcp.json or user settings.json under mcp

Local package (mcpb)
{
  "servers": {
    "delivery-schedule-milestones-late-report": {
      "type": "stdio",
      "command": "https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/delivery-schedule.mcpb",
      "args": [],
      "env": {
        "MCP_LICENSE_KEY": "<mcp_license_key>"
      }
    }
  }
}

Replace each placeholder with your own value before saving.

Check it worked: Open the Copilot chat tools picker and confirm the server is listed.

Official Visual Studio Code MCP documentation

Codex CLI command line

Configuration file: ~/.codex/config.toml

Local package (mcpb)
codex mcp add delivery-schedule-milestones-late-report -- https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/delivery-schedule.mcpb 

Replace each placeholder with your own value before saving.

Check it worked: Run codex mcp list and check the server is present.

Official Codex CLI MCP documentation

More clients (9), including automation platforms

Tools

The publisher has not disclosed a tool manifest. The tool list can only be seen by connecting to the server, which this catalogue does not do on the publisher's behalf.

Command line alternative

Yes. Delivery Schedule Milestones Late Report is available as a command line tool. The same binary does both. It has a built in MCP mode, so if the tool is already installed there is nothing more to fetch.

Command line documentation

How much of the MCP server's functionality the command line tool covers has not been assessed, so treat them as related rather than equivalent.

Detected from vendor-mcp-subcommand, vendor-nav. Confidence: low.

Repository signals

Not checked yet. Stars, licence, language and last commit date are read from the source host, and that pass has not run against this record.

Security, privacy and enterprise use

The publisher's website links no privacy policy, terms, security page or enterprise information that could be found automatically. It may still exist somewhere less obvious on their site.

Publisher

Profiles
github
Community
no subreddit linked from the publisher's site

Review platforms

CAPTERRA G2 OMR TRUSTPILOT

Ratings are not shown. G2, Trustpilot and Capterra all prohibit republishing their scores without a licence, and marking up a borrowed rating as our own would breach search engine policy. These are profile links only, and a profile may not exist for every publisher.

Frequently asked questions

What does the Delivery Schedule Milestones Late Report MCP server do?
Dated deliverables against a quote or work order. late_report says what has slipped as at any date y.
Do I need to install anything to use Delivery Schedule Milestones Late Report?
Yes. Delivery Schedule Milestones Late Report runs as a local process, so the package has to be installed on the machine where the client runs.
How do I install Delivery Schedule Milestones Late Report?
Download the MCPB bundle and install it through a client that supports bundles.
Does Delivery Schedule Milestones Late Report need an API key?
Yes. It reads 1 environment variable from the environment, so you need to supply MCP_LICENSE_KEY before the server will start.
What is MCP_LICENSE_KEY used for in Delivery Schedule Milestones Late Report?
Optional Pro license key (MCPL1....). Verified offline.
Which transport does Delivery Schedule Milestones Late Report use?
Stdio. Your client has to support that transport to connect.
Where is the source code for Delivery Schedule Milestones Late Report?
The publisher lists https://github.com/theluckystrike/mcp-servers as the source repository.
Is Delivery Schedule Milestones Late Report an official server?
It is published under the namespace com.bestremotetools, which means the publisher proved control of that domain when registering. That confirms who published it, not that it has been reviewed for quality or security.
Which version of Delivery Schedule Milestones Late Report is listed here?
Version 0.21.0, taken from the latest registry entry.