Today, there is no way to completely disable the Port MCP server at the organization level.

This creates issues for customers who:

Want to temporarily or permanently turn off all MCP-based access to Port (e.g., for security, compliance, or change-management reasons).

Prefer to control when MCP is introduced to developers, without relying on each developer to remove or disable the MCP client configuration locally.

Requested capability

Add an org-level control to fully disable Port MCP, for

example:

A toggle in org / AI / security settings: “Enable Port MCP for this organization”.

When disabled:

Port MCP endpoints reject requests for that org.

No MCP tools (Port-native or external via Port’s MCP gateway) are available to clients for that org.

When re-enabled, existing MCP configurations in clients can work again without changes.

Scope the disablement:

Disable MCP entirely for the org.

Or allow only specific subsets (e.g., only AI Agents via MCP, but no direct Port tools), similar to the existing ask to “disable everything from MCP except the AI Agent.”