> ## Documentation Index
> Fetch the complete documentation index at: https://www.narev.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP tools

> Connect flight reasoning to simulator observations, actions, and references.

You do not need to configure MCP to submit a flight. The platform connects the agent to the tools automatically. This page is for writing skills that use those tools.

## Platform-managed connection

The platform configures the `flightsim-pilot` MCP server for the selected harness. Its transport is Streamable HTTP. Harness templates contain the endpoint and authorization placeholders filled by the runner; participants do not need to commit credentials or a separate MCP configuration to their skills repository.

See [Harnesses and models](https://www.narev.ai/docs/irl-gym/submit/harnesses.md) for the actual platform templates. These templates describe this deployment, including its model routing; they are not a general installation guide for each harness.

## Start with observation

Call `get_status` with `{}` to inspect simulator connectivity and the configured aircraft, then `get_run` with `{}` for the active run. Discover groups with `list_groups` and readings with `list_readings`. Use returned IDs in later calls.

Use `read_group` with a returned `group` ID for related indications, or `read_reading` with a returned `reading_id` for one reading. `read_flight_deck_indications` provides the flight-deck indication summary; `get_function_states` reports cockpit control states.

## Retrieve the right reference

Use `search_docs` to find published aircraft guidance, airport procedures and charts. Search for a procedure name, ICAO code, runway or checklist section ID:

```json theme={null}
{"query": "YSCB ILS-Y runway 35", "limit": 5}
```

Read a returned `path` with `read_docs`. You can also read a known page directly:

```json theme={null}
{"path": "irl-gym/aircraft/manual/cockpit-interface"}
```

Search returns matching text, paths and source metadata. A page read returns its path and text content. Follow linked pages for the detailed procedure, restrictions and verification requirements. Chart illustrations accompany text references; reading the image is not required to retrieve the procedure.

Search covers the published site and filters results to IRL Gym, so it can return fewer matches than requested. If search finds nothing, read the [aircraft directory](https://www.narev.ai/docs/irl-gym/aircraft/manual) or an [airport index](https://www.narev.ai/docs/irl-gym/airports.md) by its known path. If a read fails, report the missing reference; do not substitute an unverified procedure.

## Cockpit actions

The server also exposes aircraft-specific `cockpit_*` tools generated from the configured cockpit. Each accepts one `action`, with `value` or `text` when that action requires it. Use the advertised schema and action descriptions for valid positions, units, and ranges.

Action results include `verified`, `before`, `after`, and `detail`. Read the relevant group after acting. A successful call and a completed flight procedure are different observations; use the manual's completion conditions.

Raw simulator access through `search_datarefs`, `read_dataref`, `write_dataref`, and `run_command` is no longer exposed by the pilot MCP. Use the named cockpit tools and readings. If a required control or indication is missing, use `report_issue` to describe the missing capability. The [aircraft system pages](https://www.narev.ai/docs/irl-gym/aircraft/manual) list the current MCP tool names, actions, inputs, and readings.

## Checklist progress

Read a scoped checklist and preserve its returned execution and item identifiers. `mark_checklist` records acknowledgement; it does not execute or verify cockpit actions. Notes and remarks cannot be checked. Use the returned version when making a conditional update.

## Tool reference

The navigation below this page lists the shared tools. Each page publishes the current description and complete input schema from the implementation, including required fields, defaults, enums, and constraints. Aircraft-specific cockpit tools are discovered from the active server.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.