An MCP server's Settings section, together with its header controls, is where you switch the server on for clients, reach its underlying API endpoints, and decide whether clients get notified when your tools or prompts change.
Overview
Opening a server shows its name and description in the header, an Active/Inactive toggle, and a Manage API button. A slim side navigation switches between the server's sections: Tools, Prompts, and Settings.
Activating or Deactivating the Server
Use the toggle in the server header (or the toggle on the server's row in the list). Active means clients can connect and call tools; Inactive means every client request is rejected with a "MCP Server not found" error.
Note: New servers start Inactive, so remember to switch them on once configured.
Manage API
Manage API opens the API group that was auto-created for this server — the place to see the server's endpoint URLs (the mcp/sse and mcp/messages endpoints) and manage how they're exposed, like any other API on the platform. This is where you find the URL to give an MCP client.
List-Changed Notifications
Settings offers one option:
Setting | Effect |
|---|---|
Allow clients to subscribe to changes to the list of available: Tools | Connected clients can subscribe to list-changed notifications for tools, so they're told when you add, edit, or remove a tool instead of having to re-fetch. |
Allow clients to subscribe to changes to the list of available: Prompts | Same, for prompts attached to the server. |
Changes auto-save as you tick each checkbox.
Why Isn't There a Resources Section?
The MCP protocol also defines resources, but the server configuration currently exposes only Tools, Prompts, and Settings in its navigation — resources aren't offered as a configurable section.