Moving a project from local development to the remote MigrationCoordinator at mc.shareddev.com
1aUpdate the project's .mcp.json
Point the project to the production coordinator:
{
"mcpServers": {
"MigrationCoordinator": {
"type": "http",
"url": "https://mc.shareddev.com/rpc",
"headers": {
"Mcp-Session-Id": "YourProjectName",
"X-Api-Key": "your-production-api-key"
}
}
}
}
1bRegister via Claude Code
From a Claude Code session in the project, the agent will call:
mc_register_project(name: "YourProjectName", github_repo: "SharedDev01/YourRepo")
This creates the project in the coordinator database. All other MCP tools will be blocked until an administrator configures the project settings in the dashboard.
2Fill in settings on the dashboard
Go to mc.shareddev.com → click the project → Settings tab.
| Field | Value | Example |
|---|---|---|
| Reference DB Connection | SQL auth connection to the reference database on the server | Server=localhost;Database=YourProject_ref;User Id=migcoord;Password=...;TrustServerCertificate=True; |
| Migrations Folder | Absolute path on the server | /repos/YourProject/database/migrations |
| Baseline MDF Path | Absolute path on the server | /repos/YourProject/database/baseline/YourProject.mdf |
| GitHub Repository | Owner/RepoName | SharedDev01/YourRepo |
3Click "Sync from Git" on the project dashboard
Go to the project's main page (Dashboard tab). You should see a Maintenance section with buttons.
Click Sync from Git. This will:
main, master, etc.). You don't need to rename branches.4Click "Recreate Reference DB"
This will:
After this, the deployment status banner should show green with the migration count.
5Copy the ticket sequence from the local coordinator
If the project was previously registered on the local coordinator (port 8620) and has issued ticket IDs, you need to copy the sequence to avoid ID conflicts.
On the local coordinator database:
SELECT t.LastTicketId FROM dbo.TicketSequences t
JOIN dbo.Projects p ON t.ProjectId = p.ProjectId
WHERE p.Name = 'YourProjectName'
On the remote coordinator database (MigrationCoordinator_prod):
INSERT INTO dbo.TicketSequences (ProjectId, LastTicketId)
SELECT ProjectId, <value-from-above> FROM dbo.Projects WHERE Name = 'YourProjectName'
mc_get_ticket_id on the local coordinator.6Verify everything works from Claude Code
mc_get_ticket_id — returns a ticket numbermc_register_branch — creates a dev database on the servermc_reserve_migration + mc_apply_migration — migration workflow worksmc_complete_branch — cleans up dev database7Remove from local coordinator
Once verified, the project can be removed from the local coordinator (port 8620). This is optional — leaving it is harmless.
| Error | Cause | Fix |
|---|---|---|
Project 'X' is not registered |
Project not registered on the remote coordinator | Call mc_register_project from Claude Code |
Project 'X' is registered but not fully configured |
Admin hasn't filled in project settings yet | Go to dashboard → Settings and fill in all fields |
Cannot open database "X_ref" |
Reference database doesn't exist yet | Click "Sync from Git" then "Recreate Reference DB" |
Trusted_Connection / SSPI error |
Using Windows auth on Linux | Use SQL auth: User Id=migcoord;Password=...; |
git clone failed: terminal prompts disabled |
Repo not accessible via SSH | Ensure the SSH key is added to the GitHub account |
couldn't find remote ref main |
Default branch is master, not main |
Fixed automatically — code detects default branch. If it still fails, check the repo's default branch in GitHub settings |
| Maintenance buttons not visible | Baseline MDF path not configured | Fill in the Baseline MDF Path in Settings and save |
MigrationCoordinator — Project Migration Guide — Last updated March 2026