Dev tools · Official remote MCP server

The Dev Changes MCP server,
connected in one click.

Turn described changes into reviewed pull requests: propose, triage, review, dependency audits. Connect the official Dev Changes MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.

Connect Dev Changes free How it works

Free to start · No credit card · No hosting needed

Use this server

Add Dev Changes to your AI in one minute

Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.

claude mcp add --transport http dev-changes https://mcp.openhelm.ai/dev/mcp

Run in your terminal, then restart Claude Code. The client will open the vendor's sign-in the first time you use it.

Dev Changes · https://mcp.openhelm.ai/dev/mcp

What you can do

What your AI can do with Dev Changes

Real prompts you can type the moment it's connected — no setup, no docs to read.

“What can Dev Changes do for me?”

“Show me the tools Dev Changes exposes.”

Security check

How secure is the Dev Changes MCP server?

Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Dev Changes holds up.

✓ Verified directory serverDev Changes · openhelm.ai

Official endpoint

Operated by Dev Changes (openhelm.ai) at its documented MCP endpoint — not a third-party mirror or community re-host.

OAuth sign-in — your account, your rules

You grant access from your own Dev Changes account and can revoke it there at any time. gate never sees your password.

Scanned before it goes live

gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.

Watched for drift

If Dev Changes adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.

Dev Changes's server requires OAuth, so it can't be scanned anonymously — connect it in gate and the same scan runs automatically before it goes live.

How it works

Connected in three steps

Connect your gate

Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.

Pick Dev Changes

Choose Dev Changes in the gate directory. Sign in to your Dev Changes account to grant access.

Use it anywhere

Dev Changes's tools are live in every AI client you've connected — with rules and logging built in.

Connect Dev Changes free

Free to start · No credit card · No hosting needed

Author

Who runs the Dev Changes MCP server?

openhelm.ai

Homepage More servers from openhelm.ai →

Own this server? Claim the listing →

Server facts

The Dev Changes MCP server at a glance

Endpointhttps://mcp.openhelm.ai/dev/mcp

Operated byDev Changes (openhelm.ai)

CategoryDev tools

Sign-inOAuth — your account, revocable anytime

Available in gateYes — one-click connect

Works withClaude, ChatGPT, Cursor & any MCP client

FAQ

Questions, answered

Is there an official Dev Changes MCP server?

Yes — Dev Changes operates its own remote MCP server at mcp.openhelm.ai. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.

How do I connect Dev Changes to Claude or ChatGPT?

Add gate's gateway URL to your AI client once, then pick Dev Changes in the directory. You sign in to Dev Changes via OAuth to grant access. From then on, Dev Changes's tools are available in every client you've connected to gate.

Do I need to host anything?

No. Dev Changes runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.

Is the Dev Changes MCP server safe to connect?

It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.