Wordle MCP Server: Retrieve Solution by Date
Retrieve Wordle solutions by date using the MCP server to query specific days and fetch answers instantly.
npx -y @cr2007/mcp-wordle-pythonOverview
This MCP (Model Context Protocol) server provides a lightweight HTTP interface to look up Wordle solutions by date. It hosts a small model-like service that maps calendar dates to the Wordle answer for that day, letting developers query a specific day and receive the five-letter solution instantly.
The server is useful for testing, tooling and integrations where you need a deterministic Wordle answer lookup (for example, building educational demos, recreation bots, or automated verification tools). It exposes a simple HTTP API that you can run locally or deploy to a container, and it returns structured JSON responses suitable for programmatic consumption.
Features
- Query Wordle solution by date (YYYY-MM-DD).
- Lightweight Python implementation — easy to run locally.
- Simple HTTP endpoints with JSON responses for easy integration.
- Designed to work with MCP-style clients and generic HTTP clients (curl, requests).
- Includes sample data file containing Wordle answers (can be replaced with your own data).
Installation / Configuration
Clone the repository, create a virtual environment and install dependencies:
Configure the server (environment variables are commonly supported; replace names according to the repo if different):
# Point to the JSON or CSV file that contains the Wordle answers.
# Optional: change host/port before starting the server
Start the server (typical FastAPI/uvicorn command):
After startup the server usually listens on http://localhost:8080.
Note: check the repository README or app entrypoint (app.py, main.py) for exact environment variable names and startup command if they differ.
Available Resources
The server exposes a simple HTTP interface. Typical endpoints are listed below — confirm exact paths in the repository if they differ.
| Method | Path | Description |
|---|---|---|
| GET | /wordle?date=YYYY-MM-DD | Returns the Wordle solution for the given date |
| POST | /mcp | MCP-style JSON request (model/date in body) |
| GET | /health | Health / readiness check |
Example response (JSON):
Common behaviors:
- Date format: ISO 8601 (YYYY-MM-DD).
- If the date is not present, the server usually returns a 404 or a JSON error with an explanatory message.
- The POST /mcp endpoint accepts a JSON payload and returns result in MCP-style wrapper (check repo for exact schema).
Example Requests
Using curl (GET):
Using curl (POST to MCP endpoint):
Using Python requests:
=
=
# -> TREAT
Use Cases
- Automated testing: verify a Wordle-solving algorithm against the canonical answer for a specific historical date.
- Chatbot integrations: embed a small helper that can answer “What was the Wordle on 2022-03-15?” without scraping or web lookup.
- Educational demos: show students how a deterministic model responds to date-based inputs.
- Analytics and verification: reproduce user sessions or issues by replaying the daily answer used at a specific date/time.
Example scenario — CI test that verifies solver accuracy on a known date:
- Start the MCP Wordle server in a job step.
- Query the server for the target date.
- Run your solver against the returned word and assert expected behavior.
Troubleshooting & Tips
- Ensure the data file contains entries for the date you request; otherwise the server will return an error.
- If you want production reliability, run the server behind a process manager or container (systemd, Docker).
- To extend the dataset, edit or replace the answers file and restart the server.
- Check the repository for exact endpoint names, environment variables and request schemas — they may vary slightly depending on the implementation.
Links
- GitHub: https://github.com/cr2007/mcp-wordle-python
This documentation provides the essentials to install, configure and use the MCP Wordle server to retrieve solutions by date. For implementation-specific details consult the repository source files and README.