Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MCP client implementation #1146

Closed
jmartisk opened this issue Dec 10, 2024 · 4 comments · Fixed by #1171
Closed

MCP client implementation #1146

jmartisk opened this issue Dec 10, 2024 · 4 comments · Fixed by #1171
Assignees
Labels
enhancement New feature or request

Comments

@jmartisk
Copy link
Collaborator

jmartisk commented Dec 10, 2024

This can be done after we get a LC4j version with langchain4j/langchain4j#2240 in

Idea: We could create a configuration model like this

# one stdio-based MCP server
quarkus.langchain4j.mcp.server.server1.transport-type=stdio
quarkus.langchain4j.mcp.server.server2.command=npm exec @modelcontextprotocol/[email protected]

# and one HTTP-based MCP server
quarkus.langchain4j.mcp.server.server2.transport-type=http
quarkus.langchain4j.mcp.server.server2.sse-url=http://localhost:3000/sse

and Quarkus would automatically generate a Tool provider that is backed by these two servers and register it in CDI to be picked up by AI services automatically

@jmartisk jmartisk self-assigned this Dec 10, 2024
@jmartisk
Copy link
Collaborator Author

cc @langchain4j @geoand

@geoand
Copy link
Collaborator

geoand commented Dec 10, 2024

👍🏽

@jmartisk
Copy link
Collaborator Author

BTW @edeandrea this will be a cool thing for demos :)

@geoand
Copy link
Collaborator

geoand commented Dec 11, 2024

@mkouba is working a prototype to create MCP servers. Watch quarkusio/quarkus#45054 for updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
2 participants