Produce osgi bundle metadata for mcp-annotations codebase

[scottslewis]

Currently, the mcp-annotations build does not produce OSGi metadata. I would like to use it as an osgi bundle so pr is forthcoming.

[scottslewis]

please see pr #12

[scottslewis]

These three mcp-annotation dependencies currently do not have osgi bundle meta-data (just java jars).

	<dependency>
		<groupId>com.github.victools</groupId>
		<artifactId>jsonschema-module-swagger-2</artifactId>
		<version>${jsonschema.version}</version>
	</dependency>
	
	<dependency>
		<groupId>com.github.victools</groupId>
		<artifactId>jsonschema-generator</artifactId>
		<version>${jsonschema.version}</version>
	</dependency>
	

	<dependency>
		<groupId>com.github.victools</groupId>
		<artifactId>jsonschema-module-jackson</artifactId>
		<version>${jsonschema.version}</version>
	</dependency>

This dependency

Seems to be for Java8 support...but since the min EE is java17 I don't understand why it's needed.

For this dependency

	<dependency>
		<groupId>io.swagger.core.v3</groupId>
		<artifactId>swagger-annotations-jakarta</artifactId>
		<version>${swagger-annotations.version}</version>
	</dependency>

I don't see any code references to the swagger-annotations...and doesn't declare itself in test scope.

I was able to produce bundle metadata from the 3 com.github.victools bundles and run things in a osgi environment (with the pr for mcp-annotations applied), so the extent of existing dependencies is not too bad.

But...if mcp-annotations is to be contributed/integrated with the sdk issue #10 then these dependencies will have to be used as well.

[jwflicker]

Is this regarding consumability in Eclipse? I am prototyping a embedding an MCP server inside Eclipse to enable interactivity with tools like Claude Code, Goose, and am evaluating using these annotations. Would be interested to hear if anyone else is working in this space.

[scottslewis]

Is this regarding consumability in Eclipse?

Not specifically but I would be interested in exploring that with you if you have some specific Eclipse use cases in mind.

I am prototyping a embedding an MCP server inside Eclipse to enable interactivity with tools like Claude Code, Goose, and am evaluating using these annotations. Would be interested to hear if anyone else is working in this space.

Well yeah, I'm sort of headed in similar directions but at coming at it by trying to support OSGi services-as-tools, within Eclipse or any other osgi app.

You might be interested in two things I've got going:

MCPTransports - A transport for local only (secure) MCP client <-> mcp server communication. The first alternative transport is Unix domain sockets.

MCPToolGroups - Adds the use of arbitrary Java interfaces or classes to serve as MCP 'tool groups'. Based upon the mcp-annotations tool providers approach from this project (and has code dependency on this project), but not for Spring beans...rather I'm thinking of OSGi servrices. Eclipse is made up of many OSGi services already so it would be very simple to provide MCP tool annotations for some Eclipse services...think p2/install/update, JDT, workspace model, jobs, preferences, etc. With the uds transport the security guarantees would be much stronger than http (local only). And it allows longer lasting/more dynamic MCP servers (tools added and removed dynamically).

I've got an issue to contribute the uds transport to the mcp-java-sdk here: modelcontextprotocol/java-sdk#415

The point of MCPToolGroups is to make it very easy to add tools to MCP servers...by using OSGi services with a little bit of provider/glue code (mostly in com.composent.ai.mcp.toolgroups bundle). See the Readme.md about the example.

I've proposed contributing this glue code to mcp-annotations: #13

BTW, one thing I learned when doing the example mcpserver in MCPToolGroups is that even with the osgi build information put into mcp-annotations via the above pr, mcp-annotations currently has several dependencies which do not currently have osgi bundle metadata in the available jars (e.g. classmate). I went ahead and wrapped them with OSGi metadata on my fork and put them here. I didn't get permission to redistribute these yet but if mcp-annotations is going to run in OSGi environments at all, somehow these dependencies will have to be bundlified or included into mcp-annotations...or removed as dependencies.

[scottslewis]

Is this regarding consumability in Eclipse?

Not specifically but I would be interested in exploring that with you if you have some specific Eclipse use cases in mind.

I am prototyping a embedding an MCP server inside Eclipse to enable interactivity with tools like Claude Code, Goose, and am evaluating using these annotations. Would be interested to hear if anyone else is working in this space.

BTW, one thing I learned when doing the example mcpserver in MCPToolGroups is that even with the osgi build information put into mcp-annotations via the above pr, mcp-annotations currently has several dependencies which do not currently have osgi bundle metadata in the available jars (e.g. classmate). I went ahead and wrapped them with OSGi metadata on my fork and put them here.

For everyone's info: some version of the mcp-annotation dependencies such as here are/will be necessary for any usage in Eclipse. If desired I can/will contribute build changes to mcp-annotations to wrap the necessary dependencies, but in my view it doesn't make any sense to do until this issue/pr is addressed.

BTW, it's not clear to me whether all dependencies are under the same license, known provenance, etc. As a Eclipse project lead myself for many years I'm quite sure it will be difficult to get mcp-annotations + dependencies into Eclipse (as open source project anyway...which seems necessary to me for developer and tools adoption...without the requisite IP and provenance due diligence. I'm willing to contribute help with this to mcp-annotations as an open source/community project.