pulsemcp verified Safe content atomic mcp-remote

Django Migrations

This Django Migrations MCP service, developed by mrrobotke, provides a distributed solution for managing Django migrations across multiple services. Built with Python and leveraging the Model Context Protocol, it wraps Django's migration commands into MCP endpoints, enabling seamless integration with CI/CD pipelines. The implementation focuses on enhancing migration safety through additional validation checks, including sequential order verification, conflict detection, and dependency validation. By exposing migration operations through a standardized MCP interface, this service allows for sophisticated scenarios like automated migration management in microservices architectures, centralized migration control in multi-team environments, and streamlined database schema evolution across distributed systems. It's particularly valuable for large-scale Django projects requiring coordinated database changes across multiple services or deployment environments.

Cognium trust score

100%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: database
Source: PulseMCP
Repository: github.com/mrrobotke/django-migrations-mcp
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Django Migrations from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"