Skip to content

Jentic MCP + Cursor

Goal — In a few minutes, you’ll enable Jentic MCP tools in Cursor, allowing you to find, inspect, and run external APIs directly in your coding workflow.

What you’ll get

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

Tool available in Cursor What it does
/search_apis Type what you need (e.g., "Send Discord Message", "Find New York Times Articles") and MCP lists matching APIs.
/load_execution_info Select any result to view its full spec (URL, parameters, auth requirements).
/execute Fill in the parameters and run the API or workflow – the response appears in your Cursor interaction.

Before you start

Ensure you have the following:

You need Why Quick install
Python ≥ 3.8 Required for uv/uvx and Jentic CLI. python.org
Cursor The AI coding assistant where MCP tools run. Cursor
uv / uvx runtime Launcher that runs the Jentic MCP server. Install with pip: pip install uv (any OS)  or  with Homebrew (macOS): brew install uv
If you have trouble with uvx, see Troubleshooting: Making Cursor See uvx below.

1. Get Your API Key (if you don't have one already)

To use the Jentic SDK or MCP Plugin, you must obtain your API key. The easiest way is using the Jentic CLI. You can optionally include an email address for higher rate limits and for early access to new features.

pip install jentic
jentic register --email '<your_email>'

This will print your API key and an export command to set it in your environment:

export JENTIC_UUID=<your-api-key>

Alternatively, you can use curl to register and obtain your API key:

curl -X POST https://api.jentic.com/api/v1/auth/register \
     -H "Content-Type: application/json" \
     -d '{"email": "<your_email>"}'

2. Configure Cursor to use Jentic MCP

  1. Open Cursor.

  2. Access your Cursor MCP configuration file (mcp.json):

    The easiest way to open (or create if it doesn't exist) your mcp.json is through the Cursor interface:

    • Via Cursor's Settings UI (Recommended Method):
      1. Click the cog wheel (⚙️) in the top right of the Cursor application.
      2. Select MCP from the sidebar.
      3. Click "Add new global MCP server".
      4. This will open (or create) your mcp.json file in your default text editor.

    If you prefer, or if the UI method isn't available, you can manually find and open the file:

    macOS/Linux: ~/.cursor/mcp.json

    • Terminal:
      mkdir -p ~/.cursor
      open ~/.cursor/mcp.json
      
    • File Manager:
      • Go to your home directory, show hidden files, open .cursor/mcp.json (create if missing).

    Windows: %USERPROFILE%\.cursor\mcp.json

    • File Explorer: paste %USERPROFILE%\.cursor\ in the address bar, create mcp.json if missing.
    • PowerShell:
      notepad $env:USERPROFILE\.cursor\mcp.json
      
  3. Add or update the Jentic MCP server configuration: Paste the following JSON into your mcp.json file. If the file already contains an mcpServers object with other servers, carefully add the jentic entry within it, ensuring correct JSON formatting.

{
  "mcpServers": {
    "jentic": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/jentic/jentic-tools.git@main#subdirectory=mcp",
        "mcp"
      ],
      "env": {
        "JENTIC_UUID": "<your-api-key>"
      }
    }
  }
}
  1. Save the mcp.json file.

  2. Restart Cursor for the changes to take effect.

3. (Optional) Add API keys and Environment Variables

Some APIs discovered via /search_apis and inspected with /load_execution_info will require API keys, tokens, or specific base URLs. You can add these as environment variables in your Cursor MCP configuration so they are automatically available to the Jentic MCP server.

Steps

  1. Open the same mcp.json file.
  2. Insert or update the env block inside the jentic server configuration.
  3. Save the file and restart Cursor.

Full example after adding keys

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

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

4. If something doesn’t work

What you see / Problem Try this
Jentic MCP tools not available in Cursor Check mcp.json for JSON syntax errors (e.g., missing commas, incorrect brackets). Ensure Cursor was fully restarted after any changes. Check Cursor's logs for MCP-related errors.
“command not found: uvx” (in logs or error) uvx is not in a path Cursor can see. See "Troubleshooting: Making Cursor See uvx" below for details.
API calls fail (e.g., 401/403 errors) The API likely requires authentication. Use /load_execution_info to check its requirements, then add necessary API keys/tokens to the env block in mcp.json (see Step 5). Restart Cursor.
Other errors from Jentic MCP tools Check Cursor's logs for more details. For advanced debugging, you can run the Jentic MCP server manually and inspect its direct output/logs.

Troubleshooting: Making Cursor See uvx

Cursor, like many applications, might not automatically pick up binaries added to your shell's PATH via files like .zshrc or .bashrc. 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 Cursor 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 Cursor (and any open terminals).

Option C – Hard-code the full path

Skip PATH tweaks entirely and set the absolute path to uvx / uvx.exe in the command field of mcp.json.