Skip to content

[Server] Expose Server Registry for debugging and profiling tools #74

@camilleislasse

Description

@camilleislasse

Hello! I'm working on a Symfony Web Profiler integration for MCP servers and need access to the discovered capabilities for debugging purposes.

Current Issue

  1. ServerBuilder::build() creates a Registry and populates it with discovered capabilities
  2. This Registry is passed to Handler::make() via interfaces (ReferenceRegistryInterface, ReferenceProviderInterface)
  3. Request handlers like ListToolsHandler can access capabilities via $registry->getTools()
  4. But the Registry is never exposed publicly from the Server class

The Registry class has all the needed methods:

  • getTools(): array
  • getPrompts(): array
  • getResources(): array
  • getResourceTemplates(): array

But they're only accessible internally through the MCP protocol handlers.

Proposed Solution

Add a method to expose the registry

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions