Dev Changes

ai.openhelm/dev-changes · v0.1.0

Turn described changes into reviewed pull requests: propose, triage, review, dependency audits.

Website Set it up

Connect Remote server

Terminal

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

~/.cursor/mcp.json

{
  "mcpServers": {
    "dev-changes": {
      "url": "https://mcp.openhelm.ai/dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "dev-changes": {
      "type": "http",
      "url": "https://mcp.openhelm.ai/dev/mcp"
    }
  }
}

Claude Desktop

Settings > Connectors > Add custom connector
URL: https://mcp.openhelm.ai/dev/mcp

Tools

This server asks for a key before it lists its tools. Connect it with your own key to see them.

Details

Endpoint	`https://mcp.openhelm.ai/dev/mcp` (Streamable HTTP)
First published	11 Jul 2026
Last updated	11 Jul 2026
Registry name	`ai.openhelm/dev-changes`

More other servers See all

Live status

Live, key required

Typical response: 174 ms
Latest result: 138 ms
Answered: 100% of 4 checks
Last check: 14 Nov 2026

30 days agoToday

We connect daily without credentials and run initialize and tools/list.

Pair it with live search

Agents that use Dev Changes often also need current facts. NestDaddy MCP gives your AI today's internet: web search, real-time breaking news and full page reading in one connector.

See NestDaddy MCP

For maintainers

[![NestDaddy MCP](https://nestdaddy.com/mcp/servers/ai-openhelm-dev-changes/badge.svg)](https://nestdaddy.com/mcp/servers/ai-openhelm-dev-changes)

Add the badge to your README. It turns green while your server passes our daily check. Listing details come from the official MCP registry; update them there.

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.