Skip to content

Conversation

@simasch
Copy link

@simasch simasch commented Sep 1, 2025

Description

Server Details

I've added Vaadin and jOOQ MCP servers. Vaadin provides the Vaadin server, and the jOOQ server is provided by me.

Motivation and Context

Both servers provide access to the documentation of Vaadin or jOOQ for AI agents

How Has This Been Tested?

Both MCP servers are tested with Claude.ai, Claude Code, and JetBrains Junie

Breaking Changes

No

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Copy link
Member

@olaservo olaservo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @simasch , thanks for the PR. Could you add more information on this server besides a direct link to the endpoint, such as docs on how to configure it and what tools it provides? Thanks!

@simasch
Copy link
Author

simasch commented Sep 3, 2025

Hi @olaservo

The jOOQ Tools and the installation are described here: https://jooq-mcp.fly.dev
And the Vaadin Tools are here: https://github.com/marcushellberg/vaadin-documentation-services

It was a mistake to create a single PR for two MCP servers.
How would you like me to document it?

Copy link
Member

@domdomegg domdomegg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think both of these can live in the community section. Rather than linking to the endpoints directly, link to those two documentation URLs that you have :)

Happy to accept one PR for both of them, but yes in future splitting them up can make it easier to review separately :)

@simasch
Copy link
Author

simasch commented Sep 12, 2025

@domdomegg I've updated the links

@olaservo
Copy link
Member

Thanks for your contribution to the servers list. This has been merged in this combined PR: #2914

@olaservo olaservo closed this Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants