Foundry MCP Server

This is a small stdio MCP server for local social.plus integration assistance.

The server can inspect repositories, detect design/theme signals, search hosted docs, plan harness guides/sensors, produce grounded integration plans with structured intake questions, validate setup patterns, and run detected project sensors.

Foundry is shipped as a local MCP server because SDK implementation quality depends on both hosted social.plus docs and the customer's local project context. Local MCP lets the host coding tool inspect manifests, app surfaces, design tokens, lifecycle code, and constrained command sensors while keeping source code on the customer's machine.

Remote MCP is better for hosted data or cloud actions, but a remote-only Foundry would either lose project signals or require customers to expose repository context to a hosted service. Assistant-specific skills, instruction packs, and plugins can be useful companions later, but they are not the core product boundary: Foundry keeps quality controls in MCP tool contracts, validators, sensors, and fixtures so the same package works across MCP-capable coding tools.

Frequent customer paths have dedicated guardrails:

• feed and post creation: concrete feed target, no invented communityId/targetId/feedId, no inline API keys
• notification setup: platform credentials, token source, registration after login, unregister on logout/user switch
• Live Objects/Collections: object vs collection, observed domain, lifecycle owner, loading/error states, cleanup
• monorepos: detected app surfaces can be selected with surfacePath

run_sensors is constrained to detected project commands. It does not accept arbitrary shell input.

Commands

npm install
npm run build
npm start

CLI checks:

node dist/server.js --version
node dist/server.js doctor

Full local validation:

npm run validate

Product-oriented Foundry improvement discovery:

npm run test:improvements

Docs Source

By default, docs are read from:

https://learn.social.plus/llms-full.txt

Maintainers can set SOCIAL_PLUS_DOCS_ROOT to test against a local social-plus-docs checkout.