# LibTmux.Mcp.ServerInstructions

- **Module:** LibTmux.Mcp
- **Package:** LibTmux.Mcp
- **Language:** .NET
- **Kind:** class
- **Source:** https://github.com/libtmux/libtmux-dotnet/blob/320dc64f4b8b7815842471327a5e6b84a1499bf8/src/LibTmux.Mcp/ServerInstructions.cs#L20
- **Page:** https://libtmux.org/en/dotnet/latest/mcp/reference/libtmux-mcp-serverinstructions/

What the client is told this server is for, before any tool is called.

A tool description says what one tool does. These instructions say when this
server is the right one at all, which is the question a model answers first
and cannot answer from a tool list. They carry the two things a tool
description has no room for: what must never route here, and which of two
overlapping tools to reach for.

The budget is real. Instructions are sent on every connection and sit in
context for the whole conversation, so a paragraph added here is paid for by
every call that follows.

## Members

- `Compose` (method): Composes the instructions for a running server.