What is jev-netlify-mcp?

Two parts: a key-locked Netlify proxy that exposes the TypeSafe API routes and forwards calls through Netlify AI Gateway, and a Python MCP server that gives Claude Code, Codex CLI, Claude Desktop or any MCP client two tools, jev_evaluate and jev_models.

Do I need a TypeSafe API key?

Not for the Netlify route: Netlify injects the gateway credentials, so you never create a TypeSafe API key — you lock the proxy with your own key instead. The MCP server also works directly against the TypeSafe API if you already have a key.

What does it cost to run?

The README's measurement: 18,000 Jev tokens cost 0.11 credits on the Netlify free plan, which includes 300 credits per month. The larger cost is deploying — each production deploy uses 15 credits — so the advice is to deploy once with Netlify Drop and leave it.

How do I set jev-netlify-mcp up?

Clone the repo, run pip install ., then python scripts/setup.py new-key to create your key and build dist/jev-proxy.zip. Deploy the zip with Netlify Drop (Drop sites are production deploys, which activates AI Gateway), then run setup.py set-url with your site address and setup.py check; add --live to also ask Jev one question.

Which agents and clients can connect?

Claude Code connects with claude mcp add --scope user jev -- jev-netlify-mcp; Codex CLI gets a [mcp_servers.jev] block in ~/.codex/config.toml with optional approval_mode entries; Claude Desktop gets an mcpServers entry in claude_desktop_config.json. The README says any MCP client works.

Why not set TYPESAFE_* environment variables myself?

Because if you set TYPESAFE_* variables, Netlify stops injecting the AI Gateway credentials the proxy relies on. If you want the key hash out of the deployed file, set a Netlify environment variable named JEV_PROXY_KEY_SHA256 to the hash and redeploy instead.

Where is my key stored?

In your user config file — %APPDATA%\jev-netlify-mcp\config.env on Windows or ~/.config/jev-netlify-mcp/config.env elsewhere — and, on Windows, in your user environment variables. Only its SHA-256 hash goes into the function, and setup.py never prints the key unless you run show-key.

Jev directory

CommunityJev Agents & MCP

Jev Netlify MCP

Use Jev from Claude Code, Codex CLI, Claude Desktop or any MCP client, paid for by free Netlify credits and locked with a key only you have: a key-locked proxy forwards through Netlify AI Gateway and an MCP server exposes jev_evaluate and jev_models.

See highlights Open github.com

Stars: 2
Language: Python
License: MIT
Reading time: 3 min
Published by: Community
Author: demircigoksu
Last verified: Oct 2026

demircigoksu/jev-netlify-mcp

User repository on GitHub

View on GitHub

Free, key-locked TypeSafe Jev via Netlify AI Gateway, plus an MCP server for Claude Code, Codex and Claude Desktop

Forks: 0
Last pushed: Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.

Tagscommunity catalog-import logicrw mcp netlify proxy

Works forJev for Classification Jev for Routing

Used inJev for Software & DevTools Jev for Customer Support

Languages: Python
Platforms: MCP API
Capabilities: Open sourceSelf-hostedRequires API key

Highlights

The proxy exposes POST /v1/systemone and GET /v1/models, forwarding through Netlify AI Gateway, which injects credentials — you never create a TypeSafe key.
Requests without your key get 401 and never reach the model; only the SHA-256 hash of the key is put into the deployed function.
Its measurement: 18,000 Jev tokens cost 0.11 credits on the free plan (300 credits/month); each production deploy uses 15, so deploy once and leave it.
The MCP server ships jev_evaluate and jev_models plus instructions covering atomic questions, the three question types and flagging low-confidence answers.
Works with Claude Code, Codex CLI, Claude Desktop or any MCP client; the same server can also talk to the TypeSafe API directly if you already have a key.

Quickstart

bash

pip install .
python scripts/setup.py new-key
claude mcp add --scope user jev -- jev-netlify-mcp

Watch out

Copy reviewed against the repo README on 2026-10-15; it was truncated in the Configuration section, so the full environment-variable table was not inspected. The credit figures are the project's own measurement on the Netlify free plan, not a price list; Netlify Drop sites expire without signing in, and deploy requirements can change with Netlify's own terms.

Questions about this entry

Short answers drawn from the linked project or page.

Reactions & coverage

Posts, threads, and videos about this entry from around the web.

X: Jev in front of the HeyGen MCP

X: Playwright CLI + Jev vs Playwright MCP

X: A local MCP server that cuts computer use from 23s to 0.8s. Cartwright built Cortex, a local MCP server where…

X: A side panel that drives any site's WebMCP tools

From the Jev guides

Original write-ups on what this entry is for.

MCP tool routing: Jev in front of the tool call

Oct 16, 2026

Tool menus can outgrow the context that reads them. The catalog's Jev-based routers and gates narrow the list: benchmarked tool search, per-tool scoring, fail-closed approvals, and WebMCP in the browser.

Jev Agents & MCP#mcp#tool-routing#agents

Read article

Approval policies for coding agents: hooks, guards, and gateways

Oct 16, 2026

How the Jev guard family turns coding-agent permissions into auto-approve, deny, or ask: hooks that enforce, guards that fail safe, and gateways that gate generation.

Jev Agents & MCP#coding-agents#guardrails#hooks