8 tools from the Spor MCP Server, categorised by risk level.
View the Spor policy →get_component_docs Get full documentation for a specific component: introduction, usage guidelines, and all code examples. Pass the component slug obtained from list_... get_component_examples Get only the code examples (TSX snippets) for a component. Useful when you want copy-paste-ready code without the surrounding prose. get_component_guidelines Get the design / usage guidelines for a component — when to use it, when not to, and UX best practices. get_component_props Get the props (API reference) for all sub-components of a given component. Returns a markdown table per sub-component with prop name, type, whether... get_spor_tokens Get Spor design tokens for a specific theme and category. Returns flattened color tokens with their alias names, palette keys, and hex values, plus... list_components List all documented Spor components with their slugs and a short description. Use this as the starting point to discover what components are availa... list_spor_react_exports List all exported names from the @vygruppen/spor-react package. Useful to check what components, hooks, and utilities are available to import. search_components Search for components by keyword across titles and documentation content. Returns matching components with summaries. 2/5 The Spor MCP server exposes 8 tools across 1 categories: Read.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Spor server.
Spor tools are categorised as Read (8). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept