Skip to content

docs: Document MCP editor setup and migration safety - #847

Merged
Zfinix merged 3 commits into
mainfrom
chore/document-mcp-server-tools
Sep 16, 2026
Merged

Zfinix merged 3 commits into
mainfrom
chore/document-mcp-server-tools

Conversation

@Zfinix

@Zfinix Zfinix commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Summary

The serverpod mcp-server page documented the --server-dir flag and nothing else, so there was nowhere to send a reader who wants to connect an agent to their project. It also said nothing about force, which the migration tools accept and an agent can pass on its own.

This PR:

  • Adds a "Set up your editor" section listing the six editors serverpod create configures and the config file each one gets.
  • Adds a "Set up any other MCP client" section with the two commands Serverpod registers, so clients outside that list can be wired up by hand.
  • Adds a "Migrations and your data" section warning that an agent decides on its own when to pass force, and to point the bridge at a development database.

The tool reference itself is generated and arrives separately through serverpod/serverpod#5711. Only the hand-maintained _mcp-server.md intro changes here, which the docs-sync generator preserves across runs.

@Zfinix Zfinix self-assigned this Sep 15, 2026
@Zfinix
Zfinix requested review from FXschwartz and developerjamiu and removed request for FXschwartz September 15, 2026 14:58
@Zfinix
Zfinix marked this pull request as ready for review September 16, 2026 08:28
Comment thread docs/06-concepts/cli/commands/mcp-server/_mcp-server.md Outdated
@Zfinix
Zfinix merged commit fd13f78 into main Sep 16, 2026
5 checks passed
@Zfinix
Zfinix deleted the chore/document-mcp-server-tools branch September 16, 2026 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants