Other clients
Connect Codex or any MCP client to Telys with a generic stdio server config, and verify the server starts before wiring it into a client.
Telys speaks plain MCP over stdio, so any client that can spawn a stdio server can use it — not just the ones with dedicated pages. This page covers Codex, the generic contract for everything else, and how to confirm the server runs before you wire it up.
The stdio contract
Every MCP client needs the same four facts about the Telys server:
Transport
stdio (standard input/output)
Command
telys (or the absolute path from which telys)
Arguments
["mcp"] — optionally ["mcp", "--path", "/abs/path/to/memory"]
Environment
Optional TELYS_MEMORY_PATH to choose the store
The server identifies itself as telys and negotiates protocol version 2025-06-18. It needs no API key or network access — set the memory directory and nothing else. With neither --path nor TELYS_MEMORY_PATH, it uses ~/.telys/memory.
Codex
The Codex CLI stores MCP servers as TOML in ~/.codex/config.toml. Let the installer write it:
telys mcp install --client codexOr add the table yourself:
[mcp_servers.telys]
command = "telys"
args = ["mcp"]
[mcp_servers.telys.env]
TELYS_MEMORY_PATH = "/Users/you/.telys/memory"Restart Codex to pick up the new server.
Any other MCP client
Most clients accept the JSON mcpServers shape. Add a telys entry and adapt the surrounding structure to your client's schema:
Verify the server starts
Before blaming the client, confirm the server itself runs. Start it directly from a terminal:
What you will see
Nothing is printed and the process does not exit — it blocks on stdin, waiting for a client. That is success. Press Ctrl-C to stop it. To confirm it reads a custom store, point it at one:
It behaves the same way (silent, blocking) and reads and writes collections under /tmp/telys-scratch. If the command errors immediately, the runtime is usually missing — run telys runtime verify and check MCP client won't connect.
Next steps
Last updated
Was this helpful?