yafmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIVEM_QUIET_MS | No | Silence in milliseconds on the console that closes command output capture. | 900 |
| FIVEM_SERVER_URL | No | The base URL of the FiveM server. | http://127.0.0.1:30120 |
| FIVEM_TIMEOUT_MS | No | Maximum time in milliseconds to wait for command output. | 10000 |
| FIVEM_TXADMIN_URL | No | The base URL of the txAdmin panel. | http://127.0.0.1:40120 |
| FIVEM_DEFAULT_PATH | No | The default folder used when creating a dedicated Clink agent. | ~/fx-panel |
| FIVEM_TXADMIN_PASS | Yes | The password for the txAdmin user. | |
| FIVEM_TXADMIN_USER | Yes | The txAdmin username with console.view and console.write permissions. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Operação do servidor FiveM. fivem_command executa qualquer comando no console do FXServer (via live console do txAdmin) e devolve a saída do console. Use fivem_status e fivem_players para leitura rápida, fivem_console para reler o que já passou nesta sessão, fivem_logs para os arquivos de log do txAdmin (boots e dias anteriores), e fivem_server_control apenas para start/stop/restart do processo do servidor.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fivem_commandA | Executa um comando no console do FXServer e devolve o que o console imprimiu. Aceita qualquer comando do servidor. Para (re)carregar um resource use "ensure ": ele inicia o que está parado e reinicia o que está rodando, sem precisar saber o estado antes — "start" e "restart" só valem quando falhar em um dos dois casos é justamente o que você quer. Resource novo no disco ou manifest alterado pede "refresh" antes. Também aceita stop, say, kick, set/setr , etc. A captura fecha quando o console fica quieto; comandos que demoram para responder pedem timeoutMs maior. |
| fivem_consoleA | Últimas linhas do console do servidor capturadas por esta sessão, com filtro opcional por regex. Use depois de um comando que continua imprimindo, ou para investigar erros. |
| fivem_logsA | Lê os arquivos de log do txAdmin (txData//logs): fxserver.log é o console do dia inteiro, inclusive de antes desta sessão e de boots anteriores; os dias passados ficam em fxserver_AAAA-MM-DD_*.log, e admin.log tem as ações dos admins. Use sinceBoot para ver só o que veio depois do último start do servidor, filter (regex, sem diferenciar maiúsculas) para achar erros, e list para ver os arquivos. |
| fivem_statusA | Estado do servidor: se está no ar, hostname, jogadores online, slots, game build e quantidade de resources. Lê os endpoints públicos do próprio FXServer. |
| fivem_playersA | Lista os jogadores online com id, nome, ping e identificadores. |
| fivem_server_controlA | start, stop ou restart do FXServer pelo txAdmin. Derruba todo mundo que estiver online — para recarregar um resource use fivem_command com "ensure ". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The tools mostly target distinct surfaces: command execution, log files, server lifecycle, live console tail, player list, and status. The main risk is overlap between fivem_command (which already returns console output), fivem_console, and fivem_logs, plus fivem_status duplicating the player count from fivem_players, but descriptions explicitly steer usage (e.g. server_control pointing to 'ensure' via fivem_command, console for output after a long-running command).
All names share a consistent fivem_ prefix in snake_case, which makes the set predictable. The only minor deviation is that names are noun/resource-based (fivem_console, fivem_logs, fivem_status) rather than a uniform verb_noun pattern, but they remain readable and grouped coherently.
Six tools is well-scoped for a FiveM/txAdmin server-management server, with each tool covering a clear, non-redundant facet (execute, logs, lifecycle, console, players, status). Nothing feels padded or missing at the count level.
The surface covers the core operational lifecycle: status inspection, player listing, command execution (including resource ensure/refresh), console tailing, and full server start/stop/restart. Gaps are minor, such as no direct resource/file or manifest editing and no dedicated player-management action, though these can be worked around via fivem_command.