x-api-key header that Telivy requires, so no bridge is needed.
Prerequisites
- Claude Code installed and signed in.
- Your agency’s Telivy API key from Account → Integrations. See Authentication and permissions for what the key can do.
Store the key in an environment variable
Both setup options below read the key from an environment variable namedTELIVY_API_KEY, so the key never has to be typed into a command or a shared file.
- macOS and Linux
- Windows
Add this line to your shell profile (for example
~/.zshrc or ~/.bashrc), then open a new terminal:Add the server
Choose one option. The first makes Telivy available to you in every project. The second adds Telivy to a single repository so everyone who works in it gets the same configuration, with each person supplying their own environment variable.- For you, in every project
On macOS or Linux, run:On Windows, run this in PowerShell:PowerShell reads environment variables as
$env:TELIVY_API_KEY. Written as $TELIVY_API_KEY, it refers to an unset PowerShell variable, and Claude Code would save an empty key. Run the command in a PowerShell window opened after setx, because setx does not change the window it runs in.Your shell replaces the variable with the key before the command runs, so Claude Code saves the key value itself in ~/.claude.json in your home folder. That file is private to your user account and is not part of any repository. If you regenerate the key, remove the server and add it again.Verify the connection
- Run
claude mcp listin a terminal. Thetelivyserver should show as connected. AFailed to connectstatus usually means the key is missing or wrong; see Troubleshooting. - Start Claude Code and type
/mcp. Selecttelivyto see its status and the list of Telivy tools.
Approvals
Claude Code asks for permission before it runs an MCP tool. Keep that behavior for any Telivy tool that creates, updates, rescans or uninstalls something. If you add permission rules to allow tools without a prompt, list only read-only tools by their full name, which has the formmcp__telivy__<tool name>, for example mcp__telivy__get_risk_assessments, and appears when you select a tool in /mcp. Do not allow mcp__telivy__* as a whole.
Try it
Start Claude Code and send a prompt such as:Remove the server
If you added Telivy for yourself in every project, run:telivy entry from that project’s .mcp.json. To stop using the key on this computer, also remove the TELIVY_API_KEY line from your shell profile, or run this in PowerShell on Windows: