NVIDIA / NVIDIA/OpenShell

feat(providers): add mcp category for provider profiles

Open Beginner friendly
#2,546 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

state:triage-needed
Dominant language
Rust
Stars
8.7k
Forks
1.3k
Avg merge
2d 11h
Merged PRs (30d)
253

Description

Problem Statement

Provider profiles use a category field to classify services. Current valid values: inference, source_control, agent, other, data, messaging, knowledge. There is no mcp category for MCP tool server profiles.

As MCP tool servers become a common integration pattern for agents, MCP-specific profiles need a dedicated category so developers can filter and discover them via openshell provider list-profiles.

Proposed Design

Add mcp to the valid category values in crates/openshell-providers/src/profiles.rs.

This is a one-line addition to the category enum. No schema changes, no behavioral changes.

Agent Investigation

  • Category enum parsed in crates/openshell-providers/src/profiles.rs:825 — unknown categories produce "unsupported provider profile category" error
  • McpOptionsProfile struct exists but isn't used in any built-in profile YAML
  • MCP L7 protocol (L7Protocol::Mcp) already recognized by the supervisor relay

Checklist

  • Searched for existing issues — no issue tracks adding an mcp category
  • Minimal scope — one enum value addition

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in crates/openshell-providers/src/profiles.rs around the category enum at line 825. Review the existing valid categories and the unsupported-category error, then add the requested MCP category. Done means MCP provider profile categories are accepted without schema or behavioral changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend
Issue type
Feature
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
90/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.