# mcp.toml holds literal secrets (/docs/troubleshooting/literal-secrets-mcp-toml)

What turno doctor --security means by "literal secrets in <mcp file>: <in manifest>", and the fix.

This page is for when `turno doctor --security` reports the finding below: what it means and how to fix it.

## What you see [#what-you-see]

```text
  !  literal secrets in <mcp file>: <in manifest>
     manual: store each with turno secret set <name> and write keychain:<name> in its place (args and URLs cannot hold references; see docs/mcp.md)
```

It is a warning; warnings do not change the exit code. Words in angle brackets stand for values from your machine.

## Why it happens [#why-it-happens]

A secret is written in mcp.toml itself. Env and header secrets can come from the secret store; secrets in a server's args or URL query string cannot, and stay literal.

## Fix [#fix]

Store each with turno secret set &lt;name&gt; and write keychain:&lt;name&gt; in its place (args and URLs cannot hold references; see docs/mcp.md)

No single command fixes this one, so doctor names the manual step.

Then run `turno doctor --security` again to see the row turn into `ok`.

The check lives in [`packages/turno/src/cli/security.ts`](https://github.com/wimo-dev/turno/blob/main/packages/turno/src/cli/security.ts).