The tagesschau MCP server provides access to the latest news articles and detailed information from tagesschau.de. Once running, clients can query endpoints to fetch the most recent articles across categories and to retrieve full details for a specific article by its URL. This enables you to integrate up-to-date news content into your MCP-powered flows, enabling downstream agents to summarize, compare, or analyze current events sourced from tagesschau.

To use the server, start the binary and send requests to the exposed MCP endpoints for:

• Get Latest News: Retrieve a list of the most recent articles across available categories.
• Get Article Details: Provide the article URL to obtain more granular information such as the article body, author, publish date, and metadata.

The MCP protocol routes requests to this server and returns structured responses suitable for downstream agents. Ensure your MCP configuration references the server name you use (e.g., tagesschau) and that the server is reachable by your MCP client.

Prerequisites:

• Go installed (or a prebuilt binary available in your environment)
• git

Installation steps:

1. Clone the repository git clone https://github.com/a2xdevelopment/tagesschau-mcp-server.git cd tagesschau-mcp-server

2. Build the server go mod tidy go build -o tagesschau

   The resulting executable is named 'tagesschau'

3. Run the server ./tagesschau

   Ensure it starts successfully and is listening on the expected port (default configuration)

4. (Optional) Update MCP configuration Refer to the example in the README to wire the server into your MCP configuration using the proper command and environment as needed.

Tips:

• If you customize the server port or endpoints, ensure your MCP configuration reflects those changes.
• Keep dependencies up to date by running go mod tidy before builds.
• If you encounter network or rate-limit issues with tagesschau.de, consider implementing caching or request throttling in your MCP client to reduce load.
• The env field is available for future environment variable configuration; currently it is an empty object but can be populated as needed (e.g., API keys or feature flags).