Jentic MCP + Claude Desktop¶

Goal — In a few minutes, you’ll enable Jentic MCP tools in Claude Desktop, allowing you to search, load, and execute external APIs directly in your coding workflow.

What you’ll get¶

With Jentic MCP configured in Claude Desktop, you'll gain access to powerful tools:

Tools available¶

Before you start¶

Ensure you have the following:

1. Create an Agent & get your Agent API Key¶

1. Go to app.jentic.com/sign-in and sign in to your account.
2. In Credentials, add any API secrets you'll use (e.g., Discord bot token, NYT key). These credentials will be securely stored in Jentic and automatically used by your agent.

3. Open Agents → New Agent, select which APIs/workflows this agent can access, then Generate API Key.

4. Keys are scoped to the APIs you selected and shown once.

5. Recommended: Store all API credentials in Jentic's Credentials section rather than using environment variables.
6. Set the Agent API Key as an environment variable so Claude can pass it to the MCP server:

macOS / Linux

export JENTIC_AGENT_API_KEY="<your-agent-api-key>"

Windows (PowerShell)

setx JENTIC_AGENT_API_KEY "<your-agent-api-key>"
$env:JENTIC_AGENT_API_KEY = "<your-agent-api-key>"  # current session

✅ No more jentic register, curl, or JENTIC_UUID. Use JENTIC_AGENT_API_KEY from the Agents page.

2. Configure Claude Desktop to use MCP¶

1. Quit Claude Desktop if it’s open.

2. Open or create your configuration file:

   macOS
   • In Finder press ⇧⌘G (Go → Go to Folder) and paste
   ~/Library/Application Support/Claude/ then click Go.
   • If you don’t see claude_desktop_config.json, run touch "$HOME/Library/Application Support/Claude/claude_desktop_config.json" in the terminal.
   • Double‑click the file to open it in your preferred text editor (e.g., TextEdit, VS Code, Sublime, etc.).

   Windows
   • Press Windows + R, type %APPDATA%\Claude, press Enter.
   • If the file isn’t there, right‑click ➜ New → Text Document ➜ rename to claude_desktop_config.json (be sure it’s not *.txt), then double‑click to open in Notepad.

   Linux
   • In your file manager press Ctrl + L, type ~/.config/Claude, press Enter.
   • Create the file if missing (right‑click ➜ New Document) and open it in Gedit/Kate/etc.

3. Paste the block below into the file (replace the file’s content if it’s empty):

   {
     "mcpServers": {
       "jentic": {
         "command": "uvx",
         "args": [
           "--from",
           "git+https://github.com/jentic/jentic-sdks.git@main#subdirectory=mcp",
           "mcp"
         ],
         "env": {
           "JENTIC_AGENT_API_KEY": "<your-agent-api-key>"
         }
       }
     }
   }
   

4. Save the file and re‑launch Claude Desktop.

3. Managing API Credentials¶

Recommended approach: Store all API credentials in Jentic's Credentials section when creating your agent. This keeps credentials secure and centralized.

If you need to add credentials for APIs you want to use: 1. Go back to app.jentic.com and sign in. 2. Navigate to Credentials and add any additional API keys, tokens, or secrets needed. 3. Update your agent to include the new credentials, or create a new agent with the updated credentials.

Note: Only the JENTIC_AGENT_API_KEY should be set as an environment variable. All other API credentials should be stored in Jentic's Credentials section, not as environment variables in your MCP configuration.

Optional: Using Environment Variables¶

If you prefer to use environment variables directly instead of storing credentials in Jentic, you can add them to your MCP configuration:

1. Open the same claude_desktop_config.json file.
2. Insert or update the env block inside the jentic server.
3. Save the file and restart Claude Desktop.

Example configuration with environment variables:

{
  "mcpServers": {
    "jentic": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/jentic/jentic-sdks.git@main#subdirectory=mcp",
        "mcp"
      ],
      "env": {
        "JENTIC_AGENT_API_KEY": "<your-agent-api-key>",
        "DISCORD_BOTTOKEN": "<your-discord-bot-token>",
        "OPENAI_API_KEY": "<your-openai-api-key>"
      }
    }
  }
}

Security tip: The claude_desktop_config.json file is plain text. Ensure it's stored securely, especially if it contains sensitive API keys.

4. If something doesn't work¶

Making Claude Desktop See uvx¶

Claude Desktop is a GUI app; it doesn’t read your shell profile, so binaries added to PATH in .zshrc/.bashrc may be invisible. Choose one of these options:

Option A – Homebrew / System package (macOS & Linux)¶

• Homebrew (macOS) or your distro’s package manager / a sudo pip install uv drops uvx somewhere Claude already looks:
  • /usr/local/bin on Intel Macs & most Linux distros
  • /opt/homebrew/bin on Apple Silicon

If which uvx returns a path, you’re good – skip this section.

Option B – pip / pipx / pyenv (user-local installs)¶

If uvx lives in a user-local directory, expose it via a symlink (macOS/Linux) or by adding the folder to PATH (Windows).

• macOS / Linux – symlink

  sudo ln -sf "$(which uvx)" /usr/local/bin/uvx   # use /opt/homebrew/bin on Apple Silicon
  sudo ln -sf "$(which uv)"  /usr/local/bin/uv
  

• Windows – PATH
  1. Locate the folder containing uvx.exe (e.g. %USERPROFILE%\AppData\Roaming\Python\Python311\Scripts).
  2. Add that folder to Path in Environment Variables….
  3. Restart Claude Desktop (and any open terminals).

Option C – Hard-code the full path¶

Alternatively, you can skip creating symlinks and directly specify the full path to the binary in the configuration file.

Contact Us Next