minecraft-ai-mcp

connect

Log a bot into a Minecraft server with host, port, version, and authentication, enabling gameplay.

Instructions

Connect the bot to a Minecraft server

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>",
      "username": "<username>"
    },
    "name": "connect"
  }
}

Input Schema

Name	Required	Description	Default
`auth`	No	Authentication type	offline
`host`	Yes	Server hostname or IP address
`port`	No	Server port (default: 25565)
`version`	No	Minecraft version (auto-detect if not specified)
`username`	Yes	Bot username

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.2/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description must disclose behavioral traits. It only states the action without mentioning authentication requirements, connection lifecycle, error handling, or side effects. Users are left unaware of what 'connect' entails beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, short sentence that directly states the tool's purpose with no redundant or extraneous information. It earns its place by being concise and immediately understandable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no annotations and no output schema, so the description is the primary source of context. It is too sparse, lacking information about connection setup, expected results, or behavior on failure. Even for a simple tool, more context would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers 100% of parameters with clear descriptions, so the baseline is 3. The description adds no additional parameter context, but the schema already provides sufficient semantic detail for each parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action ('Connect') and a specific resource ('the bot to a Minecraft server'), which distinguishes it from sibling tools like disconnect or get_status. It is a direct, unambiguous statement of the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the tool's purpose (connect when you need to establish a connection), but there is no explicit guidance on when to use it versus alternatives, prerequisites, or exclusions. The description does not mention any conditions such as needing to be disconnected first or handling existing connections.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.