langchain4j-mcp-server-patterns
Model Context Protocol (MCP) server implementation patterns with LangChain4j. Use when building MCP servers to extend AI capabilities with custom tools, resources, and prompt templates.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill langchain4j-mcp-server-patterns76
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has good structure with an explicit 'Use when' clause and targets a specific technical niche (MCP + LangChain4j). However, it could benefit from more concrete action verbs describing what the skill actually helps accomplish, and additional natural trigger terms that users might employ when seeking this functionality.
Suggestions
Add specific concrete actions like 'implement tool handlers, define resource providers, configure server transport, handle client connections'
Include additional trigger terms users might naturally say: 'MCP plugin', 'extend Claude', 'custom MCP tools', 'LangChain Java', 'server-side MCP'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (MCP server implementation with LangChain4j) and mentions some capabilities (custom tools, resources, prompt templates), but doesn't list concrete actions like 'create tool handlers', 'define resource endpoints', or 'configure server transport'. | 2 / 3 |
Completeness | Clearly answers both what (MCP server implementation patterns with LangChain4j) and when (building MCP servers to extend AI capabilities with custom tools, resources, and prompt templates) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'MCP', 'Model Context Protocol', 'LangChain4j', 'tools', 'resources', but missing common variations users might say like 'MCP plugin', 'server setup', 'tool integration', or 'extend Claude'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining MCP servers with LangChain4j - unlikely to conflict with other skills. The combination of 'MCP server' and 'LangChain4j' creates a distinct trigger profile. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability through executable Java code examples and good progressive disclosure via clear references to detailed documentation. The main weaknesses are moderate verbosity in introductory sections and lack of explicit end-to-end workflow with validation checkpoints for building and deploying MCP servers.
Suggestions
Add an explicit numbered workflow for building an MCP server from scratch with validation steps (e.g., 'verify server started', 'test tool execution', 'validate client connection')
Condense the 'When to Use' section to 3-4 key use cases instead of 9 bullet points
Remove the MCP Architecture explanation paragraph - Claude understands protocol architectures; keep only the diagram if needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanations (e.g., 'MCP standardizes AI application connections' and the architecture diagram are things Claude would understand). The 'When to Use' section is verbose with 9 bullet points that could be condensed. | 2 / 3 |
Actionability | Provides fully executable Java code examples throughout, including complete class implementations for ToolProvider, ResourceProvider, and PromptTemplateProvider patterns. Code is copy-paste ready with proper imports implied and clear method signatures. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for building an MCP server from start to finish. Missing validation checkpoints - for example, no guidance on verifying tool registration succeeded or testing the server before deployment. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections, well-organized patterns, and appropriate references to external files (examples.md, api-reference.md) that are one level deep and clearly signaled with descriptions of what each contains. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.