Problem

Without server-level instructions, the Port MCP Server lacks organizational context by default, leading to undeterministic responses, incorrect tool calls, and agents unfamiliar with internal terminology (e.g., "services" vs "artifacts").

Existing workarounds — Skills, custom prompts, and separate agents — all require extra distribution and setup friction that server-level instructions would eliminate entirely.

Proposed Solution

Allow platform engineers to define custom instructions at the MCP Server level that are:

Injected as the first point of context on every interaction, bypassing the need for subsequent reasoning loops

Configurable once via Port UI/API, applying universally to all developers without per-user setup

Able to encode internal terminology, blueprint priorities, and organizational guidance

Expected Outcome

Consistent, terminology-aware AI responses across the organization

Zero distribution friction compared to Skills or custom prompts

Reduced need for developers to be explicit in every query