Setup

These two register whatever your configuration is, so they are in your client's tool list before you add anything. They are why the list shows 16 tools with no key rather than the 14 market-data tools on their own.

Both are safe to call at any time. Neither returns your key, your secret, or a fingerprint of either.

setup_credentials

Opens a form for your API key and secret, so the values never enter the conversation. The form asks three things: which site the key came from (delta.exchange or the practice site demo.delta.exchange), then the key and the secret. It checks the key against Delta before saving anything, and writes ~/.delta-exchange-mcp/config.env.

Auth: No key

This tool takes no parameters. You do not call it by name either. Ask in plain language and the client picks it:

Connect my Delta Exchange account

On a client that shows the form, a saved key takes effect in the conversation you are already in. The account and trading tools appear together, without a restart, and a key that carries Trading permission can place orders from that moment.

get_connection_status

Reports whether a key is configured, which environment it points at, and whether the account and trading tools are live. Call it when a tool is missing and you want to know why.

Auth: No key

This tool takes no parameters.

What is the Delta MCP connection status?

It reconciles safe changes made to the config file outside the running process before it answers, so a key you added by hand or through uvx delta-exchange-mcp login can be picked up without a restart in some cases.

A value your client sets is read first and wins over the shared file, so a key saved to the file has no effect while the client passes its own. That case is worth knowing about if you typed your key into a client config: the form saved my key but the assistant still cannot see my account.