7timer vs Met No
A side-by-side look at the 7timer and Met No MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose 7timer for environment & nature work as a local process; choose Met No for environment & nature as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 7timer when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You want tools like
stargazing_forecast, weather_forecast.
Choose Met No when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 47/100 · Fair | 41/100 · Fair |
| 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 | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View 7timer | View Met No |
Tools & capabilities
7timer tools 2
stargazing_forecastAstronomy observing forecast from 7Timer! ASTRO — the metrics stargazers and astrophotographers use to decide if tonight is good for observing: cloud cover, atmospheric seeing (steadiness), and sky transparency, at 3-hour resolution out to 72 hours. Each point gets a human-readable label and an obs…weather_forecastGeneral weather forecast from 7Timer! CIVIL — temperature, humidity, a weather condition code (e.g. clearday, pcloudynight, lightrainday, tsday), cloud cover, wind, and precipitation type, at 3-hour resolution out to 72 hours. Keyless.
Met No tools
No tool names declared yet. Check the project README from the listing page.
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.
7timer
{
"mcpServers": {
"7timer": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-7timer"
]
}
}
}
Met No
{
"mcpServers": {
"met-no": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-met-no"
]
}
}
}
Frequently asked questions
7timer is categorized under Environment & Nature and uses a local stdio subprocess. Met No belongs to Environment & Nature and uses a local stdio subprocess. Pick 7timer for environment & nature work and Met No for environment & nature.
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.
7timer has no declared pricing — check the project's own site. Met No 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 7timer and met-no as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, 7timer has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Met No has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.