Agent skill · Backend & API

langchain4j-mcp-server-patterns

Provides LangChain4j patterns for implementing MCP (Model Context Protocol) servers, creating Java AI tools, exposing tool calling capabilities, and integrating MCP clients with AI services. Use when building a Java MCP server, implementing tool calling in Java, connecting LangChain4j to external MCP servers, or securing tool exposure for agent workflows.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill langchain4j-mcp-server-patterns-giuseppe-trisciuogli-developer-k --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Allowed tools: ReadWriteEditBashGlobGrepWebFetch
Path: skills/ai-llm/langchain4j-mcp-server-patterns-giuseppe-trisciuogli-developer-k/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# LangChain4j MCP Server Implementation Patterns ## Overview Use this skill to design and implement Model Context Protocol (MCP) integrations with LangChain4j. The main concerns are: - defining a clean tool, resource, and prompt surface - choosing the right transport and bootstrap model - filtering unsafe capabilities before exposing them to agents or applications Keep `SKILL.md` focused on the implementation flow. Use the bundled references for expanded examples and API-level detail. ## When to Use Use this skill when: - building a Java MCP server that exposes tools, resources, or prompts - integrating LangChain4j with one or more external MCP servers - wiring MCP support into a Spring Boot application - filtering available tools by tenant, user role, or runtime context - adding observability, resilience, and safe failure handling around MCP interactions - reviewing an MCP integration for prompt-injection and side-effect risks Typical trigger phrases include `langchain4j mcp`, `java mcp server`, `mcp tool provider`, `spring boot mcp`, and `connect langchain4j to mcp`. ## Instructions ### 1. Design the MCP surface before writing code Decide what the server should expose: - tools fo

What's inside
Steps it walks through
  1. Overview
  2. When to Use
  3. Instructions
  4. 1. Design the MCP surface before writing code
  5. 2. Implement providers with narrow responsibilities
  6. 3. Choose the transport intentionally
  7. 4. Bridge MCP into LangChain4j carefully
  8. 5. Add resilience and security controls
  9. 6. Validate the full workflow
  10. Examples
  11. Example 1: Minimal tool provider and stdio server bootstrap
  12. Example 2: Expose MCP tools to a LangChain4j AI service with filtering
  13. Best Practices
  14. Constraints and Warnings
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the langchain4j-mcp-server-patterns skill do?

Provides LangChain4j patterns for implementing MCP (Model Context Protocol) servers, creating Java AI tools, exposing tool calling capabilities, and integrating MCP clients with AI services. Use when building a Java MCP server, implementing tool calling in Java, connecting LangChain4j to external MCP servers, or securing tool exposure for agent workflows.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill langchain4j-mcp-server-patterns-giuseppe-trisciuogli-developer-k --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going