Bug
Running crosslink init --force updates .mcp.json to include the crosslink-agent-prompt MCP server entry, but does not write the corresponding Python server file to disk.
This leaves the MCP configuration pointing at a file that doesn't exist, causing the server to fail to start.
Steps to reproduce
- Run
crosslink init --force in a project
- Observe
.mcp.json now references crosslink-agent-prompt
- The referenced
.py file is missing from the filesystem
Expected behavior
Either:
crosslink init --force should also create/copy the agent-prompt server .py file, or
- It should not add the MCP entry if the file isn't being created
Environment
- crosslink installed via uv
- macOS
Bug
Running
crosslink init --forceupdates.mcp.jsonto include thecrosslink-agent-promptMCP server entry, but does not write the corresponding Python server file to disk.This leaves the MCP configuration pointing at a file that doesn't exist, causing the server to fail to start.
Steps to reproduce
crosslink init --forcein a project.mcp.jsonnow referencescrosslink-agent-prompt.pyfile is missing from the filesystemExpected behavior
Either:
crosslink init --forceshould also create/copy the agent-prompt server.pyfile, orEnvironment