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

Feature: View the whole MCP tool catalog across all servers in one click

Open
  • Is something wrong?
#1,200 0 comments 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
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
api, backend

Research direction

Start with the dashboard's MCP Servers page and catalog inspector, then read the GET /admin/mcp-servers/{slug}/catalog handler to see how tools, names, descriptions, and safety hints are assembled. Compare that with the tools exposed through /mcp and virtual servers. Done means a one-click view shows the combined client-visible catalog with each tool's owning server; the issue leaves search, filters, hidden tools, and an aggregate endpoint as design choices.

Written by the indexing model from the issue text.

Description

enhancement

Summary

A user asked for a way to see the full catalog of MCP tools exposed through the gateway in one place, with one click.

Today the dashboard's catalog inspector (and GET /admin/mcp-servers/{slug}/catalog) works one server at a time, so getting the full picture means opening each server's inspector separately. There's no aggregated view of everything a client of /mcp (or a virtual server) would actually see.

Request from Discord

what i would like to have: to see whole catalog of tools on one click

Source: https://discord.com/channels/1470354066524868676/1470354067875303426/1561300032819568693

Possible approach

  • A dashboard view (e.g. an "All tools" button/tab on the MCP Servers page) that lists every exposed tool across all servers, using the namespaced {slug}_{name} names clients see, with descriptions, read-only/destructive hints, and the owning server.
  • Search/filter across the combined list; optionally show tools hidden by allowed_tools / disallowed_tools separately.
  • Optionally a matching admin endpoint (e.g. GET /admin/mcp-catalog) and a per-virtual-server variant.

This issue came from a request in the GoModel Discord server (#general).

Dominant language
Go
Stars
1.2k
Forks
111
Avg merge
13h 18m
Merged PRs (30d)
90

Getting set up

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 ENTERPILOT/GoModel

All issues in ENTERPILOT/GoModel

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.