Expand description
Where the jev MCP server and the jev skill go, for each agent that can host them.
Every agent keeps its own file in its own shape, but the job is always the same: put one entry
in a config file without disturbing what is already there, and drop one SKILL.md in a
directory. This module is the pure half — paths and merged text, no filesystem — so the table
can be read in a test, and jev install stays a thin wrapper over it.
let client = install::find("codex").unwrap();
let server = ServerEntry::new("jev", "/opt/jev");
let merged = install::merge(client, Kind::Mcp, "", &server).unwrap();
assert!(merged.contains("[mcp_servers.jev]"));Structs§
- Client
Spec - One agent: what to call it, where its files live, and what shape they are in.
- Server
Entry - The server as a client writes it down.
Enums§
- Format
- How a client writes down an MCP server.
- Kind
- What is being installed.
- Scope
- Installed for this user, or into the repository in front of you.
Constants§
- CLIENTS
- The four agents, and where each keeps its things.
Functions§
- describe
- One line describing a file, for
--dry-runand for the summary. - entry
- The MCP entry, in the shape this client reads.
- file
- The file one kind of install writes for one client at one scope.
- find
- The client with this id, if it is one we know.
- ids
- Every client id, for the help text and for
--client all. - looks_
like_ ours - Whether a
SKILL.mdalready there is a copy of ours, possibly an older one. - merge
- What this file should contain once jev is installed, given what it contains now.
- toml_
table - The
[mcp_servers.<name>]table Codex reads.