Apply config writes your AI client's configuration for you, in sapio365 and in the EZ Suite products alike. This page shows what it changes, and how to set a client up yourself when the product cannot write the file, or when you prefer to edit it.
What Apply config changes on your computer
|
Client |
Configuration file |
How the product writes it |
|---|---|---|
|
Claude Code |
|
With |
|
Claude Desktop |
Microsoft Store version: |
Edits the file of each version installed. Claude Desktop starts its servers as programs, so each entry runs the |
|
Cursor |
|
Edits the file ( |
|
Visual Studio Code |
|
Edits the file ( |
|
Goose |
|
Adds Streamable HTTP extensions under |
|
ChatGPT/Codex |
|
Only with the |
-
The product only adds or removes its own entries; your other settings are kept, including the entries of other Ytria products. When it rewrites a JSON file, it lays the file out again: indentation and the order of the keys change, the content does not.
-
When the product replaces an existing file, it keeps the previous version next to it as
<file>.ytria.bak. -
Entries are recognized by their address, not their name: an entry you added by hand, under any name, counts, and the product does not add a duplicate.
Set up a client yourself
-
Make sure the server is Running in the product's AI Settings panel.
-
On the client's card, click the copy icon (Copy file path and config). The product copies the path of the client's configuration file, then the settings for both servers, its own and
mcp-ytria-docs, with their actual addresses, in that file's own format: JSON for Claude Code, Claude Desktop, Cursor and Visual Studio Code, YAML for Goose, TOML for ChatGPT/Codex. -
Open the file at the copied path (create it if it does not exist yet) and paste the settings. In a file that already has content, add the entries to the section that is already there (
mcpServers,serversorextensions) rather than adding a second one. The Codex sections go at the end ofconfig.toml. -
Save the file and restart the client. The product recognizes the entries by their address and shows the client as Configured.
While the server is stopped, the icon copies the file path only (Copy file path): the settings carry the server's address, which is known once it runs. A client shown as Unavailable has no copy icon: use the reference below, with the address from Copy address.
Claude Code keeps much of its own state in .claude.json: rather than editing that file, run the claude mcp add commands below. For Claude Desktop, Settings > Developer > Edit Config opens the file it reads.
Reference settings
These examples are for sapio365, with its default address http://localhost:33380/sapio365/, and for the documentation server, at https://mcp-docs.ytria.com/mcp/. Copied from the panel, the settings carry your actual addresses.
-
For an EZ Suite product, use its own name and address:
mcp-scanezwithhttp://localhost:33380/scanez/,mcp-databaseezwithhttp://localhost:33380/databaseez/, and so on (the name in the address is in lowercase). -
For a second instance of a product, the name ends in
-2and so does the address:mcp-sapio365-2with…/sapio365-2/. -
The
mcp-ytria-docsentry is the same for every product: one is enough. -
If you change the port later, update the entries.