Time MCP vs Lighthouse MCP
A side-by-side look at the Time MCP and Lighthouse MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Time MCP for developer tools work as a local process; choose Lighthouse MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Time MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
current_time, relative_time, days_in_month.
Choose Lighthouse MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
run_audit, get_performance_score.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 60/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 72 | 212 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | 2 |
| Full listing | View Time MCP | View Lighthouse MCP |
Tools & capabilities
Time MCP tools 6
current_timeGet the current date and time.relative_timeGet the relative time from now.days_in_monthGet the number of days in a month. If no date is provided, get the number of days in the current month.get_timestampGet the timestamp for the time.convert_timeConvert time between timezones.get_week_yearGet the week and isoWeek of the year.
Lighthouse MCP tools 2
run_auditRun a Lighthouse audit on a URLget_performance_scoreGet just the performance score for a URL
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Time MCP
{
"mcpServers": {
"time-mcp-2": {
"command": "npx",
"args": [
"-y",
"time-mcp"
]
}
}
}
Lighthouse MCP
{
"mcpServers": {
"lighthouse-mcp": {
"command": "npx",
"args": [
"lighthouse-mcp"
]
}
}
}
Frequently asked questions
Time MCP is categorized under Developer Tools and uses a local stdio subprocess. Lighthouse MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Time MCP for developer tools work and Lighthouse MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Time MCP has no declared pricing — check the project's own site. Lighthouse MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add time-mcp-2 and lighthouse-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Time MCP has a quality signal of 60/100 (Good) with 1 views, 0 installs and 72 GitHub stars. Lighthouse MCP has 64/100 (Good) with 0 views, 0 installs and 212 GitHub stars.