
Wraps the free sunrisesunset.io API to give Claude sunrise, sunset, and twilight times for any location. No authentication needed. You pass in coordinates and get back civil, nautical, and astronomical twilight data plus day length. Useful when you're building location aware features, travel tools, or anything that needs to know when the sun comes up or goes down somewhere. Hosted through Pipeworx's gateway, which also offers an ask_pipeworx tool that lets you query in plain English instead of calling the underlying API directly. Part of a larger 673+ data source collection if you want to connect to the full gateway.
Sunrise-Sunset MCP — wraps the sunrisesunset.io API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_times | Get today's sunrise, sunset, dawn, dusk, solar noon, golden hour, and day length for a given latitude and longitude. Returns all times in the location's local timezone. |
get_times_date | Get sunrise, sunset, dawn, dusk, solar noon, and golden hour times for a specific date at a location. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"sunrisesunset": {
"url": "https://gateway.pipeworx.io/sunrisesunset/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/sunrisesunset/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Sunrisesunset data" })
The gateway picks the right tool and fills the arguments automatically.
MIT