semoss-mcp-manifest

Configure MCP tool manifests for Python and Java backend integration in SEMOSS.

2|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/SEMOSS/Template --skill semoss-mcp-manifest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semoss-mcp-manifest
Source: https://github.com/SEMOSS/Template/tree/main/.claude/skills/semoss-mcp-manifest
Command: npx skills add https://github.com/SEMOSS/Template --skill semoss-mcp-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of manually configuring and wiring MCP tool manifests for the SEMOSS platform, ensuring that Python tools and Java reactors are correctly exposed to the Playground chat interface.

Core Features & Use Cases

  • Manifest Configuration: Provides guidance on editing py_mcp.json and pixel_mcp.json to register backend functions.
  • UI Mapping: Explains how to link tool resourceURIs to React routes for custom interface rendering.
  • Execution Control: Defines how to set SMSS_MCP_EXECUTION modes (auto vs ask) to manage user interaction and tool invocation.

Quick Start

Use the semoss-mcp-manifest skill to guide you through adding a new Java reactor to the pixel_mcp.json file for use in the chat interface.

Frequently Asked Questions about semoss-mcp-manifest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure an MCP tool manifest to expose backend functions in the chat interface?

Configuring an MCP tool manifest involves editing py_mcp.json or pixel_mcp.json to register Python tools and Java reactors, ensuring correct schema definition and metadata assignment for seamless tool discovery and invocation in the Playground environment.

What is the purpose of mapping resourceURIs to React routes in an MCP manifest?

Mapping resourceURIs to React routes in an MCP manifest links backend tool functions to frontend UI components, enabling custom interface rendering within the Playground when a specific tool is invoked.

How do I control tool execution modes to manage user interaction during chat invocation?

Tool execution modes are controlled by setting SMSS_MCP_EXECUTION to either auto or ask within the manifest, defining whether tools execute automatically or require user confirmation before invocation in the chat interface.

Does the SEMOSS MCP manifest support both Python and Java backend integration?

Yes, the SEMOSS MCP manifest supports both Python and Java backend integration by facilitating the mapping of backend functions to frontend routes using py_mcp.json for Python tools and pixel_mcp.json for Java reactors.

Why are my newly registered Java reactors not appearing in the Playground chat interface?

Newly registered Java reactors may not appear in the Playground chat interface if the pixel_mcp.json file lacks correct schema definition or metadata assignment, preventing seamless tool discovery and invocation.

Do I need to manually update configuration files to add a new tool to the MCP manifest?

Yes, adding a new tool requires manually editing the py_mcp.json or pixel_mcp.json configuration files to register the backend function, define its schema, and assign metadata for proper exposure to the Playground chat.