Minecraft Server Status Python API Docs | dltHub
Build a Minecraft Server Status-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
The Minecraft Server Status API provides a RESTful interface for retrieving real-time status, player counts, and server information for Java and Bedrock Minecraft servers. The REST API base URL is https://api.mcsrvstat.us/ and no authentication required, but a custom User-Agent header is mandatory.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Minecraft Server Status data in under 10 minutes.
What data can I load from Minecraft Server Status?
Here are some of the endpoints you can load from Minecraft Server Status:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| status_java | 3/<address> | GET | Full Java server status (online, ip, port, motd, players, plugins, mods, debug) | |
| status_bedrock | bedrock/3/<address> | GET | Full Bedrock server status | |
| simple_java | simple/<address> | GET | Simple HTTP status endpoint (200 OK if online, 404 if offline) | |
| simple_bedrock | bedrock/simple/<address> | GET | Simple Bedrock HTTP status endpoint | |
| icon | icon/<address> | GET | 64x64 PNG server icon (binary image response) |
How do I authenticate with the Minecraft Server Status API?
The API does not use API keys or bearer tokens; however, a descriptive and non-empty User-Agent header is required for all requests to avoid a 403 Forbidden response.
1. Get your credentials
For public status APIs like mcsrvstat.us, no formal API key is required; however, a descriptive User-Agent header (e.g., 'headers={"User-Agent": "my-service-name/1.0 (contact@example.com)"}') must be provided to avoid 403 Forbidden responses. For private services like Minecraft Server Hub, log in to your account, navigate to the 'API Access' section of your server dashboard, and generate a secure API token.
2. Add them to .dlt/secrets.toml
[sources.minecraft_server_status_source] # For services requiring a token (replace YOUR_API_TOKEN with your actual key) api_token = "YOUR_API_TOKEN" # For services requiring only a User-Agent user_agent = "my-service-name/1.0 (contact@example.com)"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Minecraft Server Status API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python minecraft_server_status_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline minecraft_server_status_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset minecraft_server_status_data The duckdb destination used duckdb:/minecraft_server_status.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads 3/
and bedrock/3/ from the Minecraft Server Status API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def minecraft_server_status_source(user_agent=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.mcsrvstat.us/", "auth": {"type": "bearer", "token": user_agent}, }, "resources": [ {"name": "status_java", "endpoint": {"path": "3/<address>"}}, {"name": "status_bedrock", "endpoint": {"path": "bedrock/3/<address>"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="minecraft_server_status_pipeline", destination="duckdb", dataset_name="minecraft_server_status_data", ) load_info = pipeline.run(minecraft_server_status_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("minecraft_server_status_pipeline").dataset() sessions_df = data.status_java.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM minecraft_server_status_data.status_java LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("minecraft_server_status_pipeline").dataset() data.status_java.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Minecraft Server Status data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Minecraft Server Status?
Request dlt skills, commands, AGENT.md files, and AI-native context.