GetAocProgressLABSCO SUMMARY
The puzzle loop without the browser tab.
Fetch the input, run your solution, submit the answer — the three steps that normally mean switching to a browser happen where the code is.
What it is
A server for the Advent of Code website. It fetches your personal puzzle input, submits answers, and reports your star count for a year. When an answer arrives too soon after the last one, it waits out the cooldown and reports progress rather than failing.
What you get
- GetInputResource returns your personal puzzle input for a year and day as an embedded resource
- SubmitAnswer submits an answer for a day and part and comes back Correct, Incorrect, TooLow or TooHigh
- GetAocProgress returns your star count for a year
- The submission rate limit is handled for you: too soon means it waits, with progress notifications, instead of erroring
- An aocinput://{year}/{day} resource template exposes the same input to clients that read resources
Requirements
Docker, and your Advent of Code session cookie passed as SESSION_COOKIE. The published image is ghcr.io/mazharenko/aoc-mcp.
Setup effort
One command plus credentials — docker run -i --rm -e SESSION_COOKIE ghcr.io/mazharenko/aoc-mcp, then supply credentials
USE CASES
Getting today's input into a file
The personal input for a given year and day comes back as a resource, ready to write out and run against.
Submitting an answer without switching windows
The verdict comes back as Correct, Incorrect, TooLow or TooHigh, which is enough to decide the next move immediately.
Trying again straight after a wrong guess
A submission inside the cooldown waits it out and reports progress, instead of handing back an error you have to time yourself.
Checking where you stand for the year
Star count for a year in one call, so progress is visible without opening the leaderboard.
3 tools
Listed in project docs. Your client may show a different list.
SubmitAnswerGetInputResourceBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- docker on PATH
- SESSION_COOKIE in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
docker run -i --rm -e SESSION_COOKIE ghcr.io/mazharenko/aoc-mcpMCP Clients
VS Code
{
"servers": {
"aoc": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SESSION_COOKIE",
"ghcr.io/mazharenko/aoc-mcp"
],
"env": {
"SESSION_COOKIE": "<YOUR_SESSION_COOKIE>"
}
}
}
}