
droneguide
io.github.CloudCorpRecords/droneguide
DroneClear Thailand: drone rules check for hobby pilots and how registration help works.
Documentation
droneguide
Can you fly your drone in Thailand, and what do you need sorted first? droneguide is a local forwarding client for the hosted DroneClear Thailand MCP service: it answers tools/list locally from the captured tool definitions and forwards every call to DroneClear, returning the answers exactly as the service sends them back.
The questions it covers are the ones hobby and tourist pilots actually ask before a trip: whether a specific drone needs CAAT and NBTC registration, whether liability insurance is required, what the flight limits are, and which areas are restricted for the place you plan to fly. It also explains, in a few lines, how the DroneClear registration-handling service works if you would rather have someone else deal with the paperwork. Nothing is checked, registered or stored locally — the package is a pipe to the service, not the service itself.
Both captured tools are built; there are no omissions. Neither tool registers anything, submits anything or sends anything — they are informational reads over published Thailand drone regulation.
The tools
drone_check— Answer a rules question for a caller-supplied drone, location and purpose: CAAT and NBTC registration, insurance, flight rules and restricted areas for the place, with public sources and a link to the fitting service information page. All parameters are optional in the served schema:weight_g,drone_model,has_camera,location,purpose(leisure_tourism,commercialorunsure),has_caat_registrationandlanguage(en,deorfr). Commercial flights get only a scope notice and a contact link; an unstated purpose gets the clarifying question back.how_droneclear_helps— Explain in a few lines how DroneClear Thailand helps hobby and tourist pilots — CAAT and NBTC registration handling, NBTC-only handling and liability insurance — with a link to the information page for each. Takes an optionallanguage(en,deorfr). Gives no prices and is not for paid or commercial flights.
Install and run
As an MCP server via npm:
npx -y @reneturcios/droneguide mcp
MCP client configuration:
{
"mcpServers": {
"droneguide": {
"command": "npx",
"args": ["-y", "@reneturcios/droneguide", "mcp"]
}
}
}
As a container:
docker run -i ghcr.io/cloudcorprecords/droneguide
docker run --rm ghcr.io/cloudcorprecords/droneguide how_droneclear_helps '{}'
CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
droneguide drone_check '{"location":"Phuket","purpose":"leisure_tourism"}'
droneguide how_droneclear_helps '{"language":"en"}'
droneguide --version
Exit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.
Configuration
DRONECLEAR_MCP_URL— Overrides the upstream endpoint, replacing the whole URL. The default is the pinned hosted endpoint,https://www.droneclearthailand.com/mcp?src=mcp(the?src=mcpquery string is part of the pinned URL). (The override variable is a reconstruction added by this rebuild.)
The upstream registry record declares no headers, so no authentication header is ever sent; the tool surface was captured keyless.
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with droneguide error:.
How forwarding works
The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.
Development
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from source
The test suite checks the served tool list against the captured surface (both tools, deep-equal, in order, with titles served as captured and no required key added to either tool), exercises the session handshake and its reuse, verifies that the default endpoint carries the ?src=mcp query string, verifies that no Authorization header is ever sent, and verifies that arguments go upstream untouched and results come back untouched.
License
MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.
@reneturcios/droneguidenpm install @reneturcios/droneguideghcr.io/cloudcorprecords/droneguide:0.1.0docker pull ghcr.io/cloudcorprecords/droneguide:0.1.0:undefinedRelated Servers
io.github.CloudCorpRecords/abandoncheck
Judge whether a dependency is maintained, from factual signals: releases, commits, archival.
io.github.CloudCorpRecords/actionbridge
Zapier exposed actions as MCP tools via a generic action runner.
io.github.CloudCorpRecords/actionpin
GitHub Actions supply-chain hardener: audit workflows for unpinned actions and build a SHA pin plan.