Connect your coding agent

Use Tokens& tool recommendations and build context inside your editor.

1Add Tokens&

Coding agent

Run this command in your terminal.

Terminal command

codex mcp add tokensand --env DAI_AGENT_INSTALL_SESSION=__TOKENSAND_AGENT_INSTALL_SESSION__ -- npx -y @dev-adoption/cli@0.1.12 mcp serve --api https://tokensand.com

Manual configuration

Add this entry to ~/.codex/config.toml if you prefer to configure the server manually.

Codex TOML

[mcp_servers.tokensand]
command = "npx"
args = ["-y", "@dev-adoption/cli@0.1.12", "mcp", "serve", "--api", "https://tokensand.com"]
env = { DAI_AGENT_INSTALL_SESSION = "__TOKENSAND_AGENT_INSTALL_SESSION__" }

2Try your first tool call

Start a new session in Codex, then send this prompt.

Use Tokens& get_account_mode, then search_tools for "support agent with auth and RAG". Show the matching tools and the receipt ID.

A successful response includes matching tools and a receipt ID.

Private context and troubleshooting

Public tool search needs no token. Your website sign-in does not connect private saved work to your coding agent.

For saved Build Packets and projects, add a scoped DAI_TOKEN to your agent configuration and set or replace the command argument with --mode developer.

For public-only use with CLI 0.1.12, set or replace the command argument with --mode public. This disables private credentials, including saved tokens. Command and saved modes take precedence over DAI_MODE.

If Tokens& tools are missing, check the server is enabled in your agent’s MCP settings and start a new session. In Codex, run codex mcp list.

Set up a private connection

[mcp_servers.tokensand] command = "npx" args = ["-y", "@dev-adoption/cli@0.1.12", "mcp", "serve", "--api", "https://tokensand.com"] env = { DAI_AGENT_INSTALL_SESSION = "__TOKENSAND_AGENT_INSTALL_SESSION__" }