How do I install the Preset MCP skill?

Run npx skillmds@latest add preset-io/preset-mcp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Preset MCP safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Preset MCP?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Preset MCP free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Preset MCP?

preset-io (@preset-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Preset MCP by preset-io — Agent Skill

Name: Preset MCP
Author: preset-io

File contents

preset-mcp

Use for Superset MCP intent, MCP tool routing, and MCP/API surface-boundary decisions.

Always

Stay on MCP tools for MCP intent.
Treat superset/superset/mcp_service as the only source of truth for MCP tool names, schemas, tags, annotations, prompts, resources, and RBAC metadata.
Call tools directly with the obvious parameters; fetch a tool's schema only after a validation error. These skills are workflow guidance, not schema definitions.
Do not use direct Preset Management API, Superset REST API, Snowflake Cortex API, curl, Python requests, exports, or database calls from this package.
If MCP cannot satisfy the request, stop and explain the missing MCP capability. Do not switch surfaces.

Decision Rules

MCP intent includes MCP tools, MCP clients, Superset MCP, Preset MCP, MCP resources, MCP prompts, tool discovery, and MCP tool errors.
Direct API intent includes API credentials, REST endpoints, OpenAPI, curl/Python requests, Management API, workspace API, and Snowflake Cortex APIs.
If the user starts with MCP intent and mentions direct API only as a fallback, keep MCP intent. Say: "No API fallback. Direct API is a different surface and requires separate explicit approval. Stop before API calls."
When the session is connected through MCP tools and the user has not named a surface, default to MCP and proceed; ask only when the user explicitly mixes both surfaces in one request.
Use a domain skill after routing: discovery, data, visualization, dashboard, sqllab, datasets, or troubleshooting.

Workflow Order

Identify whether the user requested MCP or direct API.
For MCP, choose the narrowest MCP domain skill.
Call the tool with the obvious parameters; consult its schema only after a validation error.
If MCP lacks a requested capability, explain the missing MCP capability.
Ask before changing surfaces and stop before API calls.

Retrieve

Tool categories and loading strategy: references/tool-categories.md
Surface boundary examples: references/surface-boundary.md

---name: preset-mcpdescription: Route Superset MCP tool workflows, source-of-truth checks, and surface-boundary decisions. Use only for MCP tool workflows; do not use for direct API work.---# preset-mcpUse for Superset MCP intent, MCP tool routing, and MCP/API surface-boundary decisions.## Always- Stay on MCP tools for MCP intent.- Treat `superset/superset/mcp_service` as the only source of truth for MCP tool names, schemas, tags, annotations, prompts, resources, and RBAC metadata.- Call tools directly with the obvious parameters; fetch a tool's schema only after a validation error. These skills are workflow guidance, not schema definitions.- Do not use direct Preset Management API, Superset REST API, Snowflake Cortex API, curl, Python requests, exports, or database calls from this package.- If MCP cannot satisfy the request, stop and explain the missing MCP capability. Do not switch surfaces.## Decision Rules- MCP intent includes MCP tools, MCP clients, Superset MCP, Preset MCP, MCP resources, MCP prompts, tool discovery, and MCP tool errors.- Direct API intent includes API credentials, REST endpoints, OpenAPI, curl/Python requests, Management API, workspace API, and Snowflake Cortex APIs.- If the user starts with MCP intent and mentions direct API only as a fallback, keep MCP intent. Say: "No API fallback. Direct API is a different surface and requires separate explicit approval. Stop before API calls."- When the session is connected through MCP tools and the user has not named a surface, default to MCP and proceed; ask only when the user explicitly mixes both surfaces in one request.- Use a domain skill after routing: discovery, data, visualization, dashboard, sqllab, datasets, or troubleshooting.## Workflow Order1. Identify whether the user requested MCP or direct API.2. For MCP, choose the narrowest MCP domain skill.3. Call the tool with the obvious parameters; consult its schema only after a validation error.4. If MCP lacks a requested capability, explain the missing MCP capability.5. Ask before changing surfaces and stop before API calls.## Retrieve- Tool categories and loading strategy: [references/tool-categories.md](references/tool-categories.md)- Surface boundary examples: [references/surface-boundary.md](references/surface-boundary.md)

Frequently asked questions

Preset MCP