MCP, skills, and AGENTS.md

MCP servers, skills, and AGENTS.md belong to Codex, not to CodexUse. You set them up in Codex’s own files. CodexUse adds one thing here: every profile runs against its own Codex home, so what you configure for one profile never reaches another.

One Codex home per profile

Each profile points Codex at its own home directory with its own config.toml. That is what keeps setups apart.

• An MCP server added for a work profile does not load in a personal profile.
• A server that hangs or crashes affects only the profile it belongs to.
• Switching profiles switches the whole server set with it.

MCP servers

The Model Context Protocol (MCP) gives Codex access to external tools such as docs, APIs, and internal services. To add one, open the config.toml in that profile’s Codex home and write the server block yourself:

[mcp_servers.docs]
command = "npx"
args = ["-y", "MCP_SERVER_PACKAGE", "/Users/you/Documents/docs"]

[mcp_servers.internal-api]
type = "http"
url = "https://mcp.example.com/mcp"

• A local server uses command and args, plus env or cwd when it needs them.
• A remote server uses url in place of command.
• enabled = false keeps a block in the file without starting the server.
• Codex reads the file when a session starts, so start a new session after a change.

Codex’s own documentation is the reference for the full key list.

Skills

A skill is a folder with a SKILL.md file in it. CodexUse ships a set of system skills on disk at ~/Library/Application Support/codexuse-desktop/skills/.

• There is no in-app way to create, install, or remove a skill.
• There is no skills marketplace.

AGENTS.md

AGENTS.md holds persistent agent instructions that carry across sessions.

• Global instructions apply across your Codex workspaces.
• Workspace-level instructions override the global ones when present.
• Keep them concise and specific.