Sunrise-Sunset MCP. Pinpoint golden hour timing with Lat/Long.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Sunrise-Sunset gives you precise solar data for any spot on Earth. Use this server to calculate exact sunrise, sunset, and twilight times using latitude/longitude coordinates.
It handles daylight length and lets you query past or future dates—essential for planning photography, energy projects, or large outdoor events.
What your AI agents can do
Get sunrise sunset
Gets the precise sunrise, sunset, and twilight times for any given location using latitude/longitude coordinates.
The agent gets the specific times for sunrise and sunset at a location.
You can check when civil, nautical, or astronomical twilight begins and ends for detailed light planning.
The system returns the full duration of daylight for any given day at coordinates.
Results correctly adjust to a specified timezone ID, so you don't have to worry about local offsets.
The agent runs the calculation on any date, whether it happened last year or next month.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Sunrise-Sunset MCP Server: 1 Tool for Solar Data
The single tool available calculates the exact timing of sun events—sunrise, sunset, and all levels of twilight—for specific geographical coordinates.
019e5d5bget sunrise sunset
Gets the precise sunrise, sunset, and twilight times for any given location using latitude/longitude coordinates.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Sunrise-Sunset, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
This server connects your agent to accurate astronomical data using the get_sunrise_sunset tool. You use it to calculate exact solar timings for any spot on Earth, just by feeding in latitude and longitude coordinates.
The agent gets specific times for sunrise and sunset at a location. When you run this, you're not just getting two points; you're mapping out the entire day's light cycle. You can check when civil, nautical, or astronomical twilight starts and ends, which is crucial if you're planning anything that relies on detailed light levels before dawn or after dusk.
The tool also tells you the full duration of daylight for any specific date. It calculates the total hours of sun exposure, giving you a hard number for your project plans. You don't have to worry about local offsets either; results automatically adjust based on a timezone ID you specify.
This means everything’s pegged correctly to whatever time zone you need it in.
Since this data is so precise, you can run the calculation on any date, whether that was last year or next month—it handles historical and future queries without blinking. You just feed it the coordinates and the date, and the server gives you back all the metrics.
How Sunrise-Sunset MCP Works
- 1 Your AI client calls
get_sunrise_sunsetand provides three required parameters: latitude, longitude, and a specific date. - 2 The server uses these coordinates and the date to calculate all necessary astronomical data (sun position, twilight phases, etc.).
- 3 You get back structured JSON containing the precise sunrise time, sunset time, total day length, and detailed twilight end points.
The bottom line is that you give it a place and a date, and you get all the solar timing data back in one shot.
Who Is Sunrise-Sunset MCP For?
Anyone who plans things based on natural light needs this. Photographers tired of guessing 'golden hour' timings, energy analysts calculating potential sun exposure, or event managers needing to schedule outdoor activities around perfect lighting conditions. If your project depends on the sun, you need this.
They use it to schedule large outdoor festivals, ensuring that key performances happen when the light is right (e.g., avoiding twilight or using natural sunset colors).
They calculate exact twilight timings for a shoot location over several days to ensure they capture the perfect 'blue hour' before sunrise or after sunset.
They run historical and future queries using day length data to predict how much solar power a site can generate throughout the year.
What Changes When You Connect
- Plan shoots around the 'golden hour.' Instead of guessing, use
get_sunrise_sunsetto find exact civil and nautical twilight timings for any coordinates. - Calculate total solar potential. Energy analysts can query day length data over a year or multiple locations to assess power generation without complex modeling.
- Manage outdoor events reliably. You'll know exactly when the light drops below usable levels, letting you reschedule activities using
get_sunrise_sunset’s precise timing. - Handle any date, past or future. Whether your event is next week or five years from now,
get_sunrise_sunsetprovides accurate results for that specific day's solar cycle. - Control the output timezone. The tool lets you specify a target timezone ID (
tzid), so your calculated times match local clocks without any manual conversion.
Real-World Use Cases
Planning an international film shoot
A filmmaker needs to know the perfect twilight window for Paris, but their team is based in New York. They ask their agent: 'What's the civil twilight end time in Paris on October 15th?' The agent runs get_sunrise_sunset and gets the exact timing, letting them schedule equipment rentals precisely.
Assessing a solar farm site
An energy consultant needs to know the average day length for a desert location over the next quarter. They prompt the agent with multiple coordinates and dates. The agent runs get_sunrise_sunset repeatedly, gathering total daylight hours that inform the project's viability.
Organizing a historical reenactment
A history group needs to know what natural light conditions existed at Gettysburg on July 4th, 1863. They ask their agent for the day length and sunrise/sunset times. The agent runs get_sunrise_sunset with coordinates and an old date, giving them accurate timing context.
Checking optimal viewing windows
A wildlife photographer wants to know when a specific bird species is most visible at a remote coordinate. They ask the agent for twilight data. The agent runs get_sunrise_sunset and provides the exact window where light levels are right, saving hours of scouting.
The Tradeoffs
Using general time libraries
Just calling a generic 'time converter' function with coordinates. This only gives you local clock time and nothing about the sun's position or light levels.
→
You must use get_sunrise_sunset. Always pass latitude, longitude, AND the date to the tool. If you skip the coordinates, your agent just guesses where you are.
Forgetting the timezone
Getting times for a location but not specifying the tzid (timezone ID). The result will be inaccurate if the user's local time is different from the API default.
→
Always specify the target timezone using the tzid parameter within your query to ensure the resulting hours match what people actually use.
Using today's date only
Asking for sunrise/sunset times without specifying a date or assuming 'today.' This fails when you need to plan for holidays, historical events, or future trips.
→
Always explicitly provide the desired date in your prompt. get_sunrise_sunset handles dates far in the past or future flawlessly.
When It Fits, When It Doesn't
Use this server if your task hinges on precise, geo-located timing related to celestial bodies—like photography lighting, solar energy modeling, or event scheduling based on natural light. It's non-negotiable when you need twilight phases or day length metrics.
Don't use this if all you need is simple time zone conversion (e.g., 'What time is 3 PM EST in London?'). For that, a basic calendar utility works fine. Also, don't use it if your event timing relies on non-solar factors (like opening hours or flight schedules). If the sun isn't the variable you're solving for, this tool won't help.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Sunrise-Sunset. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 1 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Scheduling events based only on local time is a guessing game.
Before having an MCP Server like Sunrise-Sunset, planning outdoor activities meant cross-referencing multiple sources: checking Google Maps for general coordinates, then opening a separate calendar to check the date, and finally trying to find specialized astronomy sites just to see if the light was good enough. It was slow, required manual data entry, and often left you with conflicting timings.
Now, your agent handles it all in one call. You tell it the location (Lat/Long), the date, and what you need (e.g., 'civil twilight'). The server runs `get_sunrise_sunset` and gives a single, accurate answer: the precise time window for perfect lighting.
Sunrise-Sunset MCP Server provides all solar timing data.
You used to only get sunrise/sunset. Now you can ask for everything in one go—civil, nautical, *and* astronomical twilight timings. You also get the total day length, which is a metric that simple time APIs never provide.
The difference is comprehensive data integrity. Your agent doesn't just give you two points (start/end); it gives you the full spectrum of light levels for your entire project.
Common Questions About Sunrise-Sunset MCP
Can I get solar data for a specific date in the future? +
Yes! Use the get_sunrise_sunset tool and provide the date parameter in YYYY-MM-DD format (e.g., '2025-12-25').
Does the tool support local timezones? +
Yes. By providing a tzid (like 'Europe/London' or 'America/New_York'), the tool returns times adjusted for that specific region.
What is the difference between civil and astronomical twilight in the results? +
The get_sunrise_sunset tool returns all phases. Civil twilight is when there is still enough light for outdoor activities, while astronomical twilight marks when the sky is completely dark for astronomical observations.
How does the Sunrise-Sunset tool handle latitude and longitude inputs? +
The tool accepts standard decimal coordinates for both latitude and longitude. You simply provide these two numbers (e.g., 34.0522, -118.2437) to pinpoint any location on Earth.
What parameters should I include when calling the get_sunrise_sunset tool? +
You must provide a latitude, longitude, and date for the calculation. The results also respect a timezone ID (tzid) if you need specific local formatting.
Are there any rate limits I should know about when using Sunrise-Sunset? +
While we don't publish hard rate limits, excessive querying may result in temporary throttling. We recommend implementing exponential backoff for high-volume automated calls to ensure stability.
If the get_sunrise_sunset tool fails, what error codes should I look out for? +
Common errors include invalid coordinates (check lat/lon format) or unsupported dates. Always check the API documentation for specific HTTP status codes and required parameters.
Does Sunrise-Sunset support historical data beyond just date queries? +
Yes, you can query historical solar data by simply passing a past date to the tool. This allows you to calculate times from any day in the recordable history of the API.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Data.gov Catalog
Access the official US Government open data catalog. Search thousands of datasets, organizations, and spatial data directly from your AI agent.
NOAA Observations — US Current Conditions
Real-time weather observations from thousands of official NWS stations: temperature, wind speed and direction, humidity, barometric pressure, visibility, and weather conditions across the United States.
World Bank Climate & Energy
Track CO2 emissions, renewable energy usage, deforestation, and electrification rates using official World Bank data.
You might also like
DealHub CPQ
Manage CPQ and sales via DealHub — create quotes, track opportunity stages, manage users, and sync CRM data directly from any AI agent.
Tesla Fleet API
Physical actuator proxy mapping explicitly native commands evaluating telemetry tracking active Tesla vehicles cleanly.
Setel Malaysia
Orchestrate Setel Malaysia payments — manage payment intents, parking sessions, and EV charging directly from any AI agent.