feststelltaste/problemrider

Create MCP Server for Problem Catalogue Access

Open

#7 opened on Aug 14, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (2 forks)auto 404
help wantedidea

Repository metrics

Stars
 (5 stars)
PR merge metrics
 (PR metrics pending)

Description

Background

AI agents could benefit from direct access to our legacy system problem catalogue through a Model Context Protocol (MCP) server, similar to how context7 provides contextual information access.

Proposed Solution

Develop an MCP server that exposes our problem catalogue data to AI agents, enabling them to:

  • Query problems by category, symptoms, or root causes
  • Search for related problems based on similarity
  • Access full problem descriptions, indicators, and examples
  • Retrieve causal relationships between problems

Example: Upstash Context7 MCP Server

Benefits

  • Agent Integration: AI agents can directly access problem knowledge
  • Contextual Assistance: Provide relevant legacy system problems during conversations
  • Automated Problem Detection: Agents can suggest related problems based on described issues
  • Knowledge Discovery: Enable semantic search across the problem space
  • Standardized Access: Use MCP protocol for consistent integration

Scope

Create an MCP server that provides structured access to the problem catalogue without requiring agents to parse markdown files directly.

Contributor guide

Research direction
Learn about the Model Context Protocol (MCP) and its server implementation. Review the example MCP server linked in the issue. Design the server to expose problem catalogue data with query capabilities. Implement endpoints for querying by category, symptoms, or root causes, and for semantic search. Ensure proper error handling and documentation.
Tech stack
javascript
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60