Where it fits
Teams extending an existing design system with React and Vue screens, schema drafting and certified charts.
- Install npx -y @oods/foundry for the full toolset.
- Draft objects from existing schema files.
- Compose React and Vue screens, or use hosted for read-only catalog work.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with OODS Foundry
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Explore what the user wants, what they assume, and which approach is worth committing to before any creative work. Use before building a feature, component, plan, or other new work where a wrong direction is costly.
Shared vocabulary for designing deep modules. Use it to design or improve a module's interface, find opportunities to deepen one, decide where a seam goes, or make code easier to test and navigate with AI, or when another skill needs the deep-module vocabulary.
Produces several sharply different interface designs for the same module, with sub-agents working in parallel. Use it when someone wants to design an API, survey interface options, weigh different module shapes, or says design it twice.
No skills found
Try a different search term or clear the filters.
Local server (full toolset)
The local stdio server exposes the full 26-tool set (27 with MCP_TOOLSET=all). The hosted https://oods-foundry.com/mcp endpoint is a read-only 9-tool subset for remote clients.
- Run the local package
Start npx -y @oods/foundry and register it as a local MCP server named oods-foundry.
- Use hosted for remote clients only
The hosted endpoint offers catalog, registry and chart tools with narrower inputs. Use local for schema drafting, screen composition and generated code.
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name oods-foundry. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
oods-foundryappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Install npx -y @oods/foundry for the full toolset. Check the result before you give the server more access.
- 3Check permissions.
The provider documents no credential for this endpoint, so there is no scope or token to review. Remove the server when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The server connects but no tools appear. Confirm the URL and transport, then restart the client.
- The first tool call times out. Try a smaller request and check the provider's status or rate limits.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
OODS Foundry documentationhttps://github.com/kneelinghorse/OODS-Foundry/blob/HEAD/packages/foundry/README.mdGitHub repositoryhttps://github.com/kneelinghorse/OODS-Foundry