Connect Your AI Agent

dayz.fyi can let an AI assistant read your server's performance measurements, so you can ask it things like "when did the server stutter last night, and did it line up with a save?" instead of reading charts yourself. This page covers who can do it, how to connect, what the assistant can and cannot see, and how to cut it off.

Who can use it

Server owners, for the servers they own.
Staff an owner has given the permission "Read server performance with an AI agent". Owners grant it through a permission group, the same way other staff permissions work. Without it, the sign-in page lists no servers and there is nothing to approve.

The agent never sees more than you do. If you lose access to a server, your agent loses it on its next question.

Connect from Claude

Open Settings → Connectors → Add custom connector.
Use the URL https://mcp.dayz.fyi/mcp.
Claude opens dayz.fyi. Sign in with Discord, then choose which servers the agent may read (or leave it on all the servers you can read performance for) and approve.

Connect from Claude Code

claude mcp add --transport http dayzfyi https://mcp.dayz.fyi/mcp

Then run /mcp inside Claude Code, pick dayzfyi, and sign in with Discord the same way.

Connect from Codex

In a terminal, run:

codex mcp add dayzfyi --url https://mcp.dayz.fyi/mcp
codex mcp login dayzfyi

Your browser opens dayz.fyi. Sign in with Discord, choose which servers the agent may read, and approve. Restart Codex if it was already open, then use /mcp to check the connection.

You can also add a Streamable HTTP server in the desktop app's Settings → MCP servers: name it dayzfyi, enter https://mcp.dayz.fyi/mcp, save, restart the connection, and authenticate.

If your Codex version cannot complete the default sign-in, try dynamic client registration:

codex mcp login dayzfyi --oauth-client-registration dcr

That connection appears as a self-registered, unverified app on the consent page. Check that you started the connection yourself before approving it.

Other AI apps that support remote connectors work the same way: give them the URL and sign in.

What it can answer

The agent has up to six read-only tools:

List my servers — which servers you can read, and whether they have recent data.
Frame-time histogram — how many server frames were fast or slow in each interval, with average and worst-second fps and player count.
Save frames — how often the server wrote its save files, and how slow those frames were next to all other frames.
Session summaries — one row per server session (a restart starts a new one): length, population, share of time spent stalled, freezes per hour. The fair way to compare sessions or servers.
Freeze events — when the server froze, for how long, how many players were online, and whether someone was connecting at the time.
Sentinel's own cost — how much server time the Sentinel Enforcer mod itself used, so you can rule it in or out. This one is coming soon; until it is switched on, the agent simply does not have it. Once it is, a server with no measurements answers "not measured yet", which is different from zero.

What the numbers mean

The frame buckets are named by their upper limit. b250 is frames between 100 and 250 milliseconds. b250p is frames of 250 ms or more. They are separate counts: never add them together and call it "slow frames over 100 ms" without including both on purpose.
A slow frame is the whole server's frame, not one mod's, and not any one player's. It is not client fps, network latency, or desync.
Time spent signing or sending data is not frame time. A long signing time does not mean a long frame, and a long frame does not mean signing was slow.
Slow frames and saves lining up is a clue, not proof. They can coincide by chance.
Compare like with like. Compare periods and servers at similar player counts; a full server is always slower than an empty one.
Freezes are not accusations. The agent gets counts, never names, so it cannot point at a player as the cause.

Limits

Read-only. The agent cannot change settings, send commands, or restart anything.
Time windows are required and capped. Each question needs a start and end time, and each kind of data has a maximum span (for example 14 days for the frame histogram and 7 days for saves and freezes). Too wide a window gets a clear error, not a quietly shortened answer.
Rate limits. Very frequent questions are slowed down; the agent is told when to retry.
Answers are size-capped. If an answer is cut off it says so and suggests a narrower window.
Connections expire. A connection lasts up to 90 days; after that you approve again.

What it never returns

Player identities. No Steam IDs, names, IP addresses, positions or chat come back through the agent. For anything about a person, use the dayz.fyi pages you already use.

Disconnect

Open Account on dayz.fyi and find Connected agents. Press Disconnect next to the agent. It stops working immediately and cannot be reconnected without a new approval. Owners can also take the permission away from a staff member at any time; their agent is then refused on its next question.