Add MCP server tool call adapter#216
Conversation
ralyodio
left a comment
There was a problem hiding this comment.
Why are oh publishing new npm packages?
|
Handled this by making the Penpot MCP wrapper workspace-private instead of publish-ready. Change in
The new core MCP stdio contract remains usable, but this PR no longer asks npm to publish a new Penpot package unless you later decide that adapter should become public. Validation rerun:
|
|
It should be public do we not already have a sh1pt npm module for integrations for use programmatically? That was the idea and point of integration |
|
You're right. I misread the first review note as "avoid publishing this package", but the issue text and the existing adapter pattern point to this being a public provider adapter. Pushed
The programmatic integration contract remains in Validation rerun:
|
Summary
tools/callhelpermcp-serversCLI adapter category@profullstack/sh1pt-mcp-server-penpot, defaulting tonpx -y @penpot/mcp@stablewith local/remote setup guidanceValidation
pnpm --filter @profullstack/sh1pt-core typecheckpnpm --filter @profullstack/sh1pt typecheckpnpm --filter @profullstack/sh1pt-mcp-server-penpot typecheckpnpm vitest run packages/mcp-servers/penpot/src/index.test.tsgit diff --checkCloses #214