setup · fcakyon — Claude Code command: what it does, how to install
setup configures Tavily MCP server credentials inside Claude Code and saves them to the plugin configuration.
Apache-2.0 ★ 1,216 updated 2026-10-24
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install tavily-tools@claude-settingsWhat setup does
The command inspects ${CLAUDE_PLUGIN_ROOT}/.mcp.json to verify the state of Tavily credentials. If the tavily.env.TAVILY_API_KEY field holds REPLACE_WITH_TAVILY_API_KEY, the script prompts for a key using AskUserQuestion. When an existing key starting with tvly- is already present, it confirms the server is set up.
Before modifying any files, the script validates user input: the key must start with tvly- and contain at least 20 characters. It then creates a backup file at ${CLAUDE_PLUGIN_ROOT}/.mcp.json.backup before writing the actual credential to .mcp.json.
Changes remain inactive until you restart Claude Code. You have to exit the active session, launch claude again, and verify the connection status using /mcp.
What it helps with
- configure Tavily MCP in Claude Code without manually editing JSON files
- validate Tavily API key format and length before saving
- create a backup copy of
.mcp.jsonbefore writing new credentials
Example prompts for the agent
- /tavily-tools:setup
- Run
/tavily-tools:setupto configure the Tavily search API key
How to install setup
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install tavily-tools@claude-settings2Manually: put the files in place
.claude/commands/setup.mdCall it with /setup. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/setup.mdCall it with /prompts:setup. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/setup.prompt.mdManually: put the files in place
.gemini/commands/setup.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about setup
How to install setup in Claude Code?
Run both marketplace commands in order: /plugin marketplace add fcakyon/claude-codex-settings, followed by /plugin install tavily-tools@claude-settings.
What does the setup command do?
It checks your current MCP configuration, validates the Tavily key format, creates a backup file, and saves the credential into .mcp.json.
Why is Tavily MCP unavailable immediately after setup?
Claude Code loads MCP configurations on startup. Exit Claude Code, run claude again, and confirm the server state with /mcp.
Source text
setup.md · Apache-2.0
---
description: Configure Tavily MCP server credentials
---
# Tavily Tools Setup
**Source:** [tavily-ai/tavily-mcp](https://github.com/tavily-ai/tavily-mcp)
Configure the Tavily MCP server with your API key.
## Step 1: Check Current Status
Read the MCP configuration from `${CLAUDE_PLUGIN_ROOT}/.mcp.json`.
Check if Tavily is configured:
- If `tavily.env.TAVILY_API_KEY` contains `REPLACE_WITH_TAVILY_API_KEY`, it needs configuration
- If it contains a value starting with `tvly-`, already configured
Report status:
- "Tavily MCP is not configured - needs an API key"
- OR "Tavily MCP is already configured"
## Step 2: Show Setup Guide
Tell the user:
```
To configure Tavily MCP, you need a Tavily API key.
Quick steps:
1. Go to app.tavily.com and sign in
2. Navigate to API Keys
3. Create a new API key
4. Copy the key (starts with tvly-)
Free tier: 1,000 searches/month
Don't need Tavily MCP? Disable it via /mcp command.
```
## Step 3: Ask for Key
Use AskUserQuestion:
- question: "Do you have your Tavily API key ready?"
- header: "Tavily Key"
- options:
- label: "Yes, I have it"
description: "I have my Tavily API key ready to paste"
- label: "No, skip for now"
description: "I'll configure it later"
If user selects "No, skip for now":
- Tell them they can run `/tavily-tools:setup` again when ready
- Remind them they can disable Tavily MCP via `/mcp` if not needed
- Exit
If user selects "Yes" or provides key via "Other":
- If they provided key in "Other" response, use that
- Otherwise, ask them to paste the key
## Step 4: Validate Key
Validate the provided key:
- Must start with `tvly-`
- Must be at least 20 characters
If invalid:
- Show error: "Invalid key format. Tavily keys start with 'tvly-'"
- Ask if they want to try again or skip
## Step 5: Update Configuration
1. Read current `${CLAUDE_PLUGIN_ROOT}/.mcp.json`
2. Create backup at `${CLAUDE_PLUGIN_ROOT}/.mcp.json.backup`
3. Update `tavily.env.TAVILY_API_KEY` value to the actual key
4. Write updated configuration back to `${CLAUDE_PLUGIN_ROOT}/.mcp.json`
## Step 6: Confirm Success
Tell the user:
```
Tavily MCP configured successfully!
IMPORTANT: Restart Claude Code for changes to take effect.
- Exit Claude Code
- Run `claude` again
To verify after restart, run /mcp and check that 'tavily' server is connected.
```
© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings
Similar slash commands
All slash commands for Agent setup: memory, context, orchestration →setup by other authors comes first.