@splunk/splunk-ui-mcp 0.1.0 → 0.3.0

package/README.md

@@ -10,7 +10,7 @@ A Model Context Protocol (MCP) server that gives AI assistants Splunk UI Design
 
 - Node.js 22 or newer
 - An MCP-compatible client (VS Code, Cursor, Windsurf, Claude Desktop, Goose, etc.)
-- Access to @splunk/react-ui and @splunk/react-icons (used for component docs and icon metadata)
+- Access to @splunk/react-ui, @splunk/react-icons, and @splunk/themes
 
 ## Install and configure
 
@@ -29,14 +29,15 @@ Use `npx` in your MCP client configuration (works in most tools):
 
 To pin a version, replace `@latest` with the desired version.
 
-## Reference (tools and resources)
+## Reference
 
-If you need the underlying tool or resource names (for debugging or client integrations), use the list below.
+If you need the underlying tool, resource, or prompt names (for debugging or client integrations), use the list below.
 
 ### Tools
 
-- `get_component_docs`: Retrieve full docs for a `@splunk/react-ui` component.
-- `find_icons`: Search `@splunk/react-icons` and return a recommended icon plus alternatives.
+- `find_component`: Find `@splunk/react-ui` components by exact name or fuzzy query; returns full docs for exact matches and suggestions otherwise.
+- `find_icon`: Search `@splunk/react-icons` and return a recommended icon plus alternatives.
+- `find_design_token`: Search `@splunk/themes` design tokens and return recommended matches.
 - `list_splunk_ui_requirements`: Return version requirements and peer dependencies.
 
 ### Resources
@@ -52,3 +53,16 @@ mcp://splunk-ui/components/{componentName}
 ```
 mcp://splunk-ui/icons/{iconName}
 ```
+
+**Design tokens**
+
+```
+mcp://splunk-ui/design-tokens/{tokenName}
+```
+
+### Prompts
+
+- `audit_code`: Audit code against Splunk UI Design System guidelines.
+- `build_ui`: Implement a Figma design or text description using Splunk UI components.
+- `create_scaffold`: Scaffold new Splunk UI standalone apps.
+- `session_feedback`: Generate quality feedback report on MCP tools, prompts, and resources.

package/lib/constants/versions.js

@@ -2,11 +2,11 @@
 // This file contains version information that gets injected at build time
 // DO NOT EDIT MANUALLY - this file is auto-generated during build
 const VERSIONS = {
-    "@splunk/react-ui": "5.8.0",
+    "@splunk/react-ui": "5.9.0",
     "react": "^16.8.0 || ^17.0.0 || ^18.0.0",
     "react-dom": "^16.8.0 || ^17.0.0 || ^18.0.0",
     "styled-components": "^5.3.10",
-    "@splunk/themes": "1.5.0",
-    "@splunk/react-icons": "5.8.0"
+    "@splunk/themes": "1.6.0",
+    "@splunk/react-icons": "5.9.0"
 };
 export default VERSIONS;

package/lib/index.js

@@ -2,10 +2,16 @@
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
 import requirements from "./tools/requirements.js";
-import findIcons from "./tools/find_icons.js";
-import getComponentDocs from "./tools/get_component_docs.js";
+import findIcon from "./tools/find_icon.js";
+import findComponent from "./tools/find_component.js";
+import findDesignToken from "./tools/find_design_token.js";
 import iconResource from "./resources/icons.js";
 import componentResource from "./resources/components.js";
+import designTokenResource from "./resources/design-tokens.js";
+import auditPrompt from "./prompts/audit/index.js";
+import buildUiPrompt from "./prompts/build-ui/index.js";
+import createScaffoldPrompt from "./prompts/create-scaffold/index.js";
+import sessionFeedbackPrompt from "./prompts/session-feedback/index.js";
 // prettier-ignore
 import packageJson from '../package.json' with { type: 'json' };
 // Create an MCP server
@@ -19,14 +25,20 @@ const server = new McpServer({
     },
 });
 // Register all tools
-const tools = [requirements, findIcons, getComponentDocs];
+const tools = [requirements, findIcon, findComponent, findDesignToken];
 tools.forEach((tool) => {
     server.registerTool(tool.name, tool.config, tool.handler);
 });
-const resources = [iconResource, componentResource];
+// Register all resources
+const resources = [iconResource, componentResource, designTokenResource];
 resources.forEach((resource) => {
     server.registerResource(resource.name, resource.template, resource.config, resource.handler);
 });
+// Register all prompts
+const prompts = [auditPrompt, buildUiPrompt, createScaffoldPrompt, sessionFeedbackPrompt];
+prompts.forEach((prompt) => {
+    server.registerPrompt(prompt.name, prompt.config, prompt.handler);
+});
 async function main() {
     try {
         const transport = new StdioServerTransport();

package/lib/prompts/audit/audit-prompt.d.ts

@@ -0,0 +1,2 @@
+declare const AUDIT_PROMPT = "Audit the code in **{{target}}** against Splunk Design System guidelines. **DO NOT modify any code.** Only report findings.\n\n1. Look up docs for each Splunk UI component used\n2. Verify the component choice matches the decision tree (e.g., Button vs Link for navigation)\n3. Verify props match the documented API\n4. Note any accessibility gaps from the component's a11y section\n5. Note any hardcoded values that could use `@splunk/themes` variables\n6. Note any Splunk UI component props that could replace custom CSS\n\nReport findings as a table with columns: File:Line, Finding, Severity, Suggested Change";
+export default AUDIT_PROMPT;

package/lib/prompts/audit/audit-prompt.js

@@ -0,0 +1,11 @@
+const AUDIT_PROMPT = `Audit the code in **{{target}}** against Splunk Design System guidelines. **DO NOT modify any code.** Only report findings.
+
+1. Look up docs for each Splunk UI component used
+2. Verify the component choice matches the decision tree (e.g., Button vs Link for navigation)
+3. Verify props match the documented API
+4. Note any accessibility gaps from the component's a11y section
+5. Note any hardcoded values that could use \`@splunk/themes\` variables
+6. Note any Splunk UI component props that could replace custom CSS
+
+Report findings as a table with columns: File:Line, Finding, Severity, Suggested Change`;
+export default AUDIT_PROMPT;

package/lib/prompts/audit/audit.d.ts

@@ -0,0 +1,16 @@
+import { GetPromptResult } from '@modelcontextprotocol/sdk/types.js';
+import { z } from 'zod';
+declare const auditPrompt: {
+    name: string;
+    config: {
+        title: string;
+        description: string;
+        argsSchema: {
+            target: z.ZodOptional<z.ZodString>;
+        };
+    };
+    handler: ({ target }: {
+        target?: string;
+    }) => GetPromptResult;
+};
+export default auditPrompt;

package/lib/prompts/audit/audit.js

@@ -0,0 +1,36 @@
+import { z } from 'zod';
+import AUDIT_PROMPT from "./audit-prompt.js";
+const auditPrompt = {
+    name: 'audit_code',
+    config: {
+        title: 'Audit Code Against Splunk UI Guidelines',
+        description: 'Returns a structured audit workflow for checking code against ' +
+            'Splunk UI design system guidelines. Read-only — does not modify code.',
+        argsSchema: {
+            target: z
+                .string()
+                .optional()
+                .describe('File path or directory to audit (e.g., "src/App.tsx", "src/components"). ' +
+                'Defaults to the current working directory if not provided.'),
+        },
+    },
+    handler: ({ target }) => {
+        const trimmed = target?.trim();
+        const resolvedTarget = trimmed && trimmed.length > 0 ? trimmed : process.cwd();
+        const isDefault = !trimmed;
+        const prompt = AUDIT_PROMPT.replaceAll('{{target}}', resolvedTarget);
+        const confirmation = isDefault
+            ? `The target directory defaulted to ${resolvedTarget}. Confirm this is correct before proceeding.\n\n`
+            : '';
+        return {
+            description: `Splunk UI audit workflow for ${resolvedTarget}`,
+            messages: [
+                {
+                    role: 'user',
+                    content: { type: 'text', text: `${confirmation}${prompt}` },
+                },
+            ],
+        };
+    },
+};
+export default auditPrompt;

package/lib/prompts/audit/index.d.ts

@@ -0,0 +1 @@
+export { default } from './audit.ts';

package/lib/prompts/audit/index.js

@@ -0,0 +1 @@
+export { default } from "./audit.js";

package/lib/prompts/build-ui/build-figma-design-prompt.d.ts

@@ -0,0 +1,2 @@
+declare const BUILD_FIGMA_DESIGN_PROMPT = "You are a senior frontend engineer, implement the design at {{figmaLink}} as a React component using the Splunk Design System.\n\n1. Read the design context from the Figma link\n2. Verify Splunk UI package versions are correct\n3. Look up component docs for each component BEFORE writing code\n4. Use Splunk UI components with their documented props and patterns\n5. Use styled-components with `@splunk/themes` variables and mixins for any styling that falls outside component props\n6. Flag any design values (colors, sizes, spacing) that don't map to a Splunk UI component prop or theme variable";
+export default BUILD_FIGMA_DESIGN_PROMPT;

package/lib/prompts/build-ui/build-figma-design-prompt.js

@@ -0,0 +1,9 @@
+const BUILD_FIGMA_DESIGN_PROMPT = `You are a senior frontend engineer, implement the design at {{figmaLink}} as a React component using the Splunk Design System.
+
+1. Read the design context from the Figma link
+2. Verify Splunk UI package versions are correct
+3. Look up component docs for each component BEFORE writing code
+4. Use Splunk UI components with their documented props and patterns
+5. Use styled-components with \`@splunk/themes\` variables and mixins for any styling that falls outside component props
+6. Flag any design values (colors, sizes, spacing) that don't map to a Splunk UI component prop or theme variable`;
+export default BUILD_FIGMA_DESIGN_PROMPT;

package/lib/prompts/build-ui/build-ui-prompt.d.ts

@@ -0,0 +1,2 @@
+declare const BUILD_UI_PROMPT = "You are a senior frontend engineer, build **{{description}}** as a React component using the Splunk Design System.\n\n1. Verify Splunk UI package versions are correct\n2. Look up component docs BEFORE using any Splunk UI component\n3. Follow component decision trees to choose the right component (e.g., Button vs Link for navigation)\n4. Use `@splunk/themes` variables and mixins for custom styling\n5. Flag any requirements that don't map to existing components or theme values";
+export default BUILD_UI_PROMPT;

package/lib/prompts/build-ui/build-ui-prompt.js

@@ -0,0 +1,8 @@
+const BUILD_UI_PROMPT = `You are a senior frontend engineer, build **{{description}}** as a React component using the Splunk Design System.
+
+1. Verify Splunk UI package versions are correct
+2. Look up component docs BEFORE using any Splunk UI component
+3. Follow component decision trees to choose the right component (e.g., Button vs Link for navigation)
+4. Use \`@splunk/themes\` variables and mixins for custom styling
+5. Flag any requirements that don't map to existing components or theme values`;
+export default BUILD_UI_PROMPT;

package/lib/prompts/build-ui/build-ui.d.ts

@@ -0,0 +1,16 @@
+import { GetPromptResult } from '@modelcontextprotocol/sdk/types.js';
+import { z } from 'zod';
+declare const buildUiPrompt: {
+    name: string;
+    config: {
+        title: string;
+        description: string;
+        argsSchema: {
+            input: z.ZodOptional<z.ZodString>;
+        };
+    };
+    handler: ({ input }: {
+        input?: string;
+    }) => GetPromptResult;
+};
+export default buildUiPrompt;

package/lib/prompts/build-ui/build-ui.js

@@ -0,0 +1,62 @@
+import { z } from 'zod';
+import BUILD_UI_PROMPT from "./build-ui-prompt.js";
+import BUILD_FIGMA_DESIGN_PROMPT from "./build-figma-design-prompt.js";
+const buildUiPrompt = {
+    name: 'build_ui',
+    config: {
+        title: 'Build UI',
+        description: 'Returns a structured workflow for implementing a UI from a text description or Figma design ' +
+            'using the Splunk UI Design System.',
+        argsSchema: {
+            input: z
+                .string()
+                .optional()
+                .describe('Text description of the feature/UI to build (e.g., "a settings page with a form") ' +
+                'OR a Figma link (e.g., "https://figma.com/design/...").'),
+        },
+    },
+    handler: ({ input }) => {
+        const trimmed = input?.trim();
+        if (!trimmed) {
+            return {
+                description: 'Splunk UI build workflow — awaiting input',
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: 'Please provide either:\n- A text description of the UI to build (e.g., "a settings page with a form and save button")\n- OR a Figma link (e.g., https://figma.com/design/...)',
+                        },
+                    },
+                ],
+            };
+        }
+        // Auto-detect Figma links (must be actual Figma domain with file ID)
+        // Valid format: https://figma.com/{type}/{fileId}/...
+        // File ID must be non-empty alphanumeric string
+        const isFigmaLink = /^https?:\/\/(www\.)?figma\.com\/(design|file|board|make)\/[A-Za-z0-9]+/.test(trimmed);
+        if (isFigmaLink) {
+            const prompt = BUILD_FIGMA_DESIGN_PROMPT.replaceAll('{{figmaLink}}', trimmed);
+            return {
+                description: `Splunk UI build workflow — Figma design: ${trimmed}`,
+                messages: [
+                    {
+                        role: 'user',
+                        content: { type: 'text', text: prompt },
+                    },
+                ],
+            };
+        }
+        const prompt = BUILD_UI_PROMPT.replaceAll('{{description}}', trimmed);
+        return {
+            description: 'Splunk UI build workflow — text description',
+            messages: [
+                {
+                    role: 'user',
+                    content: { type: 'text', text: prompt },
+                },
+            ],
+        };
+    },
+};
+export default buildUiPrompt;

package/lib/prompts/build-ui/index.d.ts

@@ -0,0 +1 @@
+export { default } from './build-ui.ts';

package/lib/prompts/build-ui/index.js

@@ -0,0 +1 @@
+export { default } from "./build-ui.js";

package/lib/prompts/create-scaffold/create-scaffold-prompt.d.ts

@@ -0,0 +1,2 @@
+declare const STANDALONE_PROMPT = "Scaffold a new Splunk UI standalone app named \"{{appName}}\".\n\nBEFORE running any commands, check if the current directory is empty:\n- If the directory is NOT empty, STOP and tell the user: \"The current directory must be empty. Please run this in an empty directory or create a new one.\"\n- If the directory IS empty, proceed with the commands below.\n\nRun these commands ONE AT A TIME in the foreground. Wait for FULL completion before the next:\n\n```sh\nnpx --yes @splunk/create@latest --mode=standalone {{appName}}\nyarn install\n```\n\nCRITICAL RULES:\n- Check directory is empty FIRST before running any commands\n- Use the Bash tool for EACH command separately\n- Set timeout to 300000ms (5 minutes) for npx and yarn install commands\n- NEVER use run_in_background parameter\n- NEVER add & to background commands\n- Wait for exit code 0 before proceeding to next command\n- Do NOT add any additional flags beyond what's shown\n- Do NOT pipe input with printf or echo\n\nAfter ALL commands complete successfully, output ONLY this message:\n\n---\nYour app {{appName}} is ready!\n\nNext steps:\n1. Open a new terminal tab\n2. Run: `yarn dev`\n3. A browser window will open with the app\n---";
+export default STANDALONE_PROMPT;

package/lib/prompts/create-scaffold/create-scaffold-prompt.js

@@ -0,0 +1,34 @@
+const STANDALONE_PROMPT = `Scaffold a new Splunk UI standalone app named "{{appName}}".
+
+BEFORE running any commands, check if the current directory is empty:
+- If the directory is NOT empty, STOP and tell the user: "The current directory must be empty. Please run this in an empty directory or create a new one."
+- If the directory IS empty, proceed with the commands below.
+
+Run these commands ONE AT A TIME in the foreground. Wait for FULL completion before the next:
+
+\`\`\`sh
+npx --yes @splunk/create@latest --mode=standalone {{appName}}
+yarn install
+\`\`\`
+
+CRITICAL RULES:
+- Check directory is empty FIRST before running any commands
+- Use the Bash tool for EACH command separately
+- Set timeout to 300000ms (5 minutes) for npx and yarn install commands
+- NEVER use run_in_background parameter
+- NEVER add & to background commands
+- Wait for exit code 0 before proceeding to next command
+- Do NOT add any additional flags beyond what's shown
+- Do NOT pipe input with printf or echo
+
+After ALL commands complete successfully, output ONLY this message:
+
+---
+Your app {{appName}} is ready!
+
+Next steps:
+1. Open a new terminal tab
+2. Run: \`yarn dev\`
+3. A browser window will open with the app
+---`;
+export default STANDALONE_PROMPT;

package/lib/prompts/create-scaffold/create-scaffold.d.ts

@@ -0,0 +1,16 @@
+import { GetPromptResult } from '@modelcontextprotocol/sdk/types.js';
+import { z } from 'zod';
+declare const createScaffoldPrompt: {
+    name: string;
+    config: {
+        title: string;
+        description: string;
+        argsSchema: {
+            appName: z.ZodString;
+        };
+    };
+    handler: ({ appName }: {
+        appName?: string;
+    }) => GetPromptResult;
+};
+export default createScaffoldPrompt;

package/lib/prompts/create-scaffold/create-scaffold.js

@@ -0,0 +1,60 @@
+import { z } from 'zod';
+import STANDALONE_PROMPT from "./create-scaffold-prompt.js";
+const createScaffoldPrompt = {
+    name: 'create_scaffold',
+    config: {
+        title: 'Create Splunk UI App',
+        description: 'Returns a step-by-step workflow for scaffolding a new Splunk UI app (standalone Vite-based app).',
+        argsSchema: {
+            appName: z
+                .string()
+                .describe('Name for the new app (e.g., "MyApp"). Letters only - no numbers, no spaces, no special characters.'),
+        },
+    },
+    handler: ({ appName }) => {
+        const trimmed = appName?.trim();
+        if (!trimmed) {
+            return {
+                description: 'Splunk UI scaffold workflow — missing app name',
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: 'ERROR: appName parameter is required but was empty. This prompt cannot be invoked without a valid app name.',
+                        },
+                    },
+                ],
+            };
+        }
+        // Enforce letters only - no numbers, spaces, or special characters.
+        // appName is interpolated directly into shell commands in the scaffold template,
+        // so invalid characters must be rejected here.
+        if (!/^[a-zA-Z]+$/.test(trimmed)) {
+            const validationError = 'Use only letters - no numbers, no spaces, no special characters.';
+            return {
+                description: 'Splunk UI scaffold workflow — invalid app name',
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: `"${trimmed}" is not a valid app name. ${validationError} (e.g., "MyApp")`,
+                        },
+                    },
+                ],
+            };
+        }
+        const prompt = STANDALONE_PROMPT.replaceAll('{{appName}}', trimmed);
+        return {
+            description: `Splunk UI scaffold workflow — standalone app "${trimmed}"`,
+            messages: [
+                {
+                    role: 'user',
+                    content: { type: 'text', text: prompt },
+                },
+            ],
+        };
+    },
+};
+export default createScaffoldPrompt;

package/lib/prompts/create-scaffold/index.d.ts

@@ -0,0 +1 @@
+export { default } from './create-scaffold.ts';

package/lib/prompts/create-scaffold/index.js

@@ -0,0 +1 @@
+export { default } from "./create-scaffold.js";

package/lib/prompts/session-feedback/index.d.ts

@@ -0,0 +1 @@
+export { default } from './session-feedback.ts';

package/lib/prompts/session-feedback/index.js

@@ -0,0 +1 @@
+export { default } from "./session-feedback.js";

package/lib/prompts/session-feedback/session-feedback-prompt.d.ts

@@ -0,0 +1,2 @@
+declare const SESSION_FEEDBACK_PROMPT = "# Splunk UI MCP Feedback Report\n\nYou are providing feedback to the Splunk UI MCP team about the tools, prompts, and resources used in this session.\n\n## Your Task\n\nReview this session and report on the **quality and effectiveness of MCP tools, prompts, and resources**. Focus on what worked well and what needs improvement from the MCP team's perspective.\n\n**Important:** Only report on what was actually used. If everything worked well, say so - don't invent issues.\n\n## Report Structure\n\n### 1. Session Overview\n\n**User's Goal:**\n[Brief description of what they wanted to accomplish]\n\n**What Was Used:**\nReview your conversation history and list ONLY the MCP tools, prompts, and resources you actually used:\n\n- **Tools:** [List with call counts - e.g., \"find_component (3 calls: Button, Card, Modal)\"]\n- **Prompts:** [List which ones - e.g., \"audit_code, build_ui, create_scaffold\"]\n- **Resources:** [List what docs you accessed - e.g., \"Button component docs, spacing tokens\"]\n\n### 2. Issues Encountered\n\nFor each issue you encountered, report:\n\n**Issue: [Brief title]**\n- **Category:** [Tool / Prompt / Resource]\n- **Specific item:** [Which tool/prompt/component/token]\n- **What happened:** [Detailed description with evidence]\n- **Expected behavior:** [What should have happened]\n- **Impact:** [Blocked / Slowed / Minor inconvenience]\n- **Suggested fix:** [What the MCP team should change]\n\n**\uD83D\uDD04 Inefficiency Patterns:**\nIf you called the same tool multiple times or had to retry operations, explain:\n- Which tool/resource and how many times\n- Why multiple attempts were needed\n- What could prevent this pattern\n\n**If no issues:** State \"No significant issues encountered in this session.\"\n\n### 3. What Worked Well\n\nHighlight MCP features that were particularly helpful:\n- Tools that provided complete, accurate information on first try\n- Prompts with clear, effective guidance\n- Documentation that was comprehensive and easy to use\n- Features that saved time or effort\n\nBe specific with examples.\n\n### 4. Top Recommendations (Prioritized)\n\nList your top 2-5 recommendations in priority order:\n\n**1. [Recommendation title]**\n- **Priority:** [Critical / Important / Enhancement]\n  - Critical = Blocked progress or caused significant delays\n  - Important = Slowed progress or required workarounds\n  - Enhancement = Would improve experience but not blocking\n- **Issue:** [What needs to be fixed/added]\n- **Benefit:** [How this would help users]\n\n**2. [Next recommendation]**\n[Same structure]\n\n### 5. Missing Capabilities\n\nIf there were tools, prompts, or resources that would have helped but don't exist:\n- **What's missing:** [Description]\n- **Use case:** [When/why it's needed]\n- **Current workaround:** [What you do instead, if anything]\n\n---\n\n## Guidelines\n\n**Before writing the report:**\n1. Scroll back through this entire conversation\n2. Count each tool call (find_component, find_icon, find_design_token, list_splunk_ui_requirements)\n3. Note specific components/tokens/icons you looked up\n4. Identify which prompts were invoked\n5. List which documentation you actually read\n\n**Focus on MCP quality, not AI behavior:**\n- \u2705 \"find_component returned incomplete prop documentation for Button\"\n- \u274C \"I should have read the Button docs more carefully\"\n\n**Be specific and actionable:**\n- \u2705 \"Button component docs missing 'size' prop - shows 'variant' but not size options\"\n- \u274C \"Documentation could be better\"\n\n**Include evidence:**\n- Reference specific tool calls that had issues\n- Quote confusing or incorrect information\n- Note which documentation sections were incomplete\n\n**Be honest:**\n- If everything worked great, say so\n- Don't invent problems to fill the template\n- It's OK to have a short report for a smooth session\n\n**The goal:** Help the MCP team improve their tools, prompts, and resources. Usage data provides context, but quality feedback is the primary objective.\n\n---\n\n## Begin Your Feedback Report\n\nReview this session and generate the report following the structure above.";
+export default SESSION_FEEDBACK_PROMPT;

package/lib/prompts/session-feedback/session-feedback-prompt.js

@@ -0,0 +1,113 @@
+const SESSION_FEEDBACK_PROMPT = `# Splunk UI MCP Feedback Report
+
+You are providing feedback to the Splunk UI MCP team about the tools, prompts, and resources used in this session.
+
+## Your Task
+
+Review this session and report on the **quality and effectiveness of MCP tools, prompts, and resources**. Focus on what worked well and what needs improvement from the MCP team's perspective.
+
+**Important:** Only report on what was actually used. If everything worked well, say so - don't invent issues.
+
+## Report Structure
+
+### 1. Session Overview
+
+**User's Goal:**
+[Brief description of what they wanted to accomplish]
+
+**What Was Used:**
+Review your conversation history and list ONLY the MCP tools, prompts, and resources you actually used:
+
+- **Tools:** [List with call counts - e.g., "find_component (3 calls: Button, Card, Modal)"]
+- **Prompts:** [List which ones - e.g., "audit_code, build_ui, create_scaffold"]
+- **Resources:** [List what docs you accessed - e.g., "Button component docs, spacing tokens"]
+
+### 2. Issues Encountered
+
+For each issue you encountered, report:
+
+**Issue: [Brief title]**
+- **Category:** [Tool / Prompt / Resource]
+- **Specific item:** [Which tool/prompt/component/token]
+- **What happened:** [Detailed description with evidence]
+- **Expected behavior:** [What should have happened]
+- **Impact:** [Blocked / Slowed / Minor inconvenience]
+- **Suggested fix:** [What the MCP team should change]
+
+**🔄 Inefficiency Patterns:**
+If you called the same tool multiple times or had to retry operations, explain:
+- Which tool/resource and how many times
+- Why multiple attempts were needed
+- What could prevent this pattern
+
+**If no issues:** State "No significant issues encountered in this session."
+
+### 3. What Worked Well
+
+Highlight MCP features that were particularly helpful:
+- Tools that provided complete, accurate information on first try
+- Prompts with clear, effective guidance
+- Documentation that was comprehensive and easy to use
+- Features that saved time or effort
+
+Be specific with examples.
+
+### 4. Top Recommendations (Prioritized)
+
+List your top 2-5 recommendations in priority order:
+
+**1. [Recommendation title]**
+- **Priority:** [Critical / Important / Enhancement]
+  - Critical = Blocked progress or caused significant delays
+  - Important = Slowed progress or required workarounds
+  - Enhancement = Would improve experience but not blocking
+- **Issue:** [What needs to be fixed/added]
+- **Benefit:** [How this would help users]
+
+**2. [Next recommendation]**
+[Same structure]
+
+### 5. Missing Capabilities
+
+If there were tools, prompts, or resources that would have helped but don't exist:
+- **What's missing:** [Description]
+- **Use case:** [When/why it's needed]
+- **Current workaround:** [What you do instead, if anything]
+
+---
+
+## Guidelines
+
+**Before writing the report:**
+1. Scroll back through this entire conversation
+2. Count each tool call (find_component, find_icon, find_design_token, list_splunk_ui_requirements)
+3. Note specific components/tokens/icons you looked up
+4. Identify which prompts were invoked
+5. List which documentation you actually read
+
+**Focus on MCP quality, not AI behavior:**
+- ✅ "find_component returned incomplete prop documentation for Button"
+- ❌ "I should have read the Button docs more carefully"
+
+**Be specific and actionable:**
+- ✅ "Button component docs missing 'size' prop - shows 'variant' but not size options"
+- ❌ "Documentation could be better"
+
+**Include evidence:**
+- Reference specific tool calls that had issues
+- Quote confusing or incorrect information
+- Note which documentation sections were incomplete
+
+**Be honest:**
+- If everything worked great, say so
+- Don't invent problems to fill the template
+- It's OK to have a short report for a smooth session
+
+**The goal:** Help the MCP team improve their tools, prompts, and resources. Usage data provides context, but quality feedback is the primary objective.
+
+---
+
+## Begin Your Feedback Report
+
+Review this session and generate the report following the structure above.`;
+export default SESSION_FEEDBACK_PROMPT;

package/lib/prompts/session-feedback/session-feedback.d.ts

@@ -0,0 +1,11 @@
+import { GetPromptResult } from '@modelcontextprotocol/sdk/types.js';
+declare const sessionFeedbackPrompt: {
+    name: string;
+    config: {
+        title: string;
+        description: string;
+        argsSchema: {};
+    };
+    handler: () => GetPromptResult;
+};
+export default sessionFeedbackPrompt;

package/lib/prompts/session-feedback/session-feedback.js

@@ -0,0 +1,22 @@
+import SESSION_FEEDBACK_PROMPT from "./session-feedback-prompt.js";
+const sessionFeedbackPrompt = {
+    name: 'session_feedback',
+    config: {
+        title: 'Generate MCP Session Feedback Report',
+        description: 'Prompts the AI to provide feedback about the quality and effectiveness of MCP tools, ' +
+            'prompts, and resources used in the current session, with actionable recommendations for the MCP team.',
+        argsSchema: {},
+    },
+    handler: () => {
+        return {
+            description: 'Splunk UI MCP session feedback report',
+            messages: [
+                {
+                    role: 'user',
+                    content: { type: 'text', text: SESSION_FEEDBACK_PROMPT },
+                },
+            ],
+        };
+    },
+};
+export default sessionFeedbackPrompt;

package/lib/prompts/types.d.ts

@@ -0,0 +1,8 @@
+import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+type RegisterPromptArgs = Parameters<McpServer['registerPrompt']>;
+export type PromptDefinition = {
+    name: RegisterPromptArgs[0];
+    config: RegisterPromptArgs[1];
+    handler: RegisterPromptArgs[2];
+};
+export {};

package/lib/resources/components.js

@@ -1,8 +1,8 @@
 import { ResourceTemplate } from '@modelcontextprotocol/sdk/server/mcp.js';
-import { filterByKeywords } from '@splunk/ui-utils/filter.js';
-import { getComponentList, getComponentDocs, getComponentInfo, } from "../utils/component-catalog.js";
+import { getComponentList, getComponentNames, getComponentDocs, getComponentInfo, searchComponents, } from "../utils/component-catalog.js";
 export const COMPONENT_RESOURCE_NAME = 'splunk-ui-components';
 export const COMPONENT_RESOURCE_URI_BASE = 'mcp://splunk-ui/components';
+const CATEGORY_SEARCH_MIN_QUERY_LENGTH = 3;
 /**
  * Creates an MCP resource URI for a component
  */
@@ -76,12 +76,13 @@ const componentResourceTemplate = new ResourceTemplate(`${COMPONENT_RESOURCE_URI
     complete: {
         componentName: async (value) => {
             const input = value?.toString() ?? '';
+            const componentNames = getComponentNames();
+            const includeCategory = input.trim().length >= CATEGORY_SEARCH_MIN_QUERY_LENGTH;
             // Return all component names if no input is provided
             if (!input) {
-                return getComponentList().map((component) => component.name);
+                return componentNames;
             }
-            const componentNames = getComponentList().map((component) => component.name);
-            return filterByKeywords(componentNames, input);
+            return searchComponents(input, { includeCategory });
         },
     },
 });
@@ -101,7 +102,12 @@ const componentResource = {
         // Prefer the componentName param, but fall back to extracting from the path.
         let componentName;
         if (typeof componentNameParam === 'string' && componentNameParam.length > 0) {
-            componentName = componentNameParam;
+            try {
+                componentName = decodeURIComponent(componentNameParam);
+            }
+            catch {
+                throw new Error(`Invalid component name in resource params: ${componentNameParam}`);
+            }
         }
         else {
             // Extract from path, but exclude 'components' itself