Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

MCP Apps: foundation (package, capability detection, hello-world status card, fallback policy)

Open
  • Is something wrong?
#78 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
api, cli, documentation, testing

Research direction

Start by reviewing SDK 2.x upgrade issue #39 and draft PR #76, then verify whether Claude Desktop renders a ui:// resource from a locally launched stdio server. Trace the existing get_location_and_mapping and get_current_user tools, compare the two tools/list discovery goldens, and record client versions and results in docs/mcp-sdk-2-testing.md. Done means UI-capable clients receive metadata while terminal-client JSON remains byte-for-byte unchanged.

Written by the indexing model from the issue text.

Description

Area: MCP Apps Priority: P3 Type: Feature

Umbrella for interactive UI over the MCP server. Depends on the SDK 2.x upgrade (#39, draft PR #76): the ModelContextProtocol.Extensions.Apps package starts at 2.0.

Scope

  • Reference ModelContextProtocol.Extensions.Apps, call the builder registration, and serve one embedded HTML resource at a ui://timepro/status address: current user, tenant name, environment (prod/non-prod), accounting feature state, repo mapping for the working directory. Backed by the existing get_location_and_mapping and get_current_user tools; no new data paths.
  • Capability detection: attach UI metadata only when the client advertised the io.modelcontextprotocol/ui extension (initialize capabilities, or per-request _meta under 2026-07-28). Terminal clients (Claude Code, Codex CLI) keep today's JSON byte-for-byte; the discovery goldens for a non-UI client must not change.
  • Sandbox rules: the page only ever sees tool results; no API keys, no direct HTTP; every write goes back through an existing tool so the CLI-first guards apply.
  • Regression harness: a second tools/list golden captured with the UI capability advertised, and a test that the two differ only by UI metadata.
  • First-hour check before any real view: confirm Claude Desktop renders a ui:// resource served by a locally launched stdio server (unverified as of 2026-09-13). If it does not, this whole area waits.

Verify against

Claude Desktop first, then VS Code Copilot. Record client versions in docs/mcp-sdk-2-testing.md.

Dominant language
C#
Stars
3
Forks
0
Avg merge
7m
Merged PRs (30d)
30

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No 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.

More from SSWConsulting/TimePro.Tools

All issues in SSWConsulting/TimePro.Tools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.