No way to subclass MCP

[NicolasAnquetil]

I tried to create my own MCP server by subclassing MCP but the initialization process only looks at the server class itself

MCPMessageProcessor >> addHandlersFromPragmasIn: anObject

	( Pragma allNamed: #jrpc: in: anObject class )
		do: [ :pragma | ...

since the pragma is in methods define by MCP itself, this does not work for subclasses of MCP

One straightforward solution would be to redefine it to look up the inheritance hierarchy:

addHandlersFromPragmasIn: anObject
      anObject class withAllSuperclasses reverseDo: [ :cls |
			(Pragma allNamed: #jrpc: in: aClass) do: [ :pragma | ...

[Gabriel-Darbord]

Hello Nicolas,
I'm wondering why you need to subclass MCP?
Is it to expand the JSON-RPC domain to include resources and prompts?
I'll see what can be done to be able to subclass MCP.

[NicolasAnquetil]

I want to define my own MCP server (see MooseMCP) with its own set of tools.

I should not be able to make any change to the code, only call Moose tools.

This could be done by unregistering tools I don't want and resgistering mine, but I find it more convenient to simply define a subclass of MCP that overloads toolRegistry to use a subclass of MCPToolRegistry that overrides defaultRegistrations...

[Gabriel-Darbord]

#152 adds the MCP subclassing capability.
I've also been thinking about "profiles" for a while: a profile contains a set of tools (and their visibility configuration), resources, prompts, etc., which should fit your case :)

[Gabriel-Darbord]

#153 adds profiles.
You can subclass MCPProfile, MCP, both, or neither (and still do what you want, with more or less boilerplate).

With only subclassing MCPProfile to define your tools:

MooseMCPProfile >> toolClasses

	^ { Moose MCP tools... }

Then adopt the profile:

mcp := MCP profile: MooseMCPProfile new.

[NicolasAnquetil]

OK thanks, I will look at it