spring-projects / spring-projects/spring-ai

Allow defining multiple MCP servers in a single application, with parametrized paths

Open
#2,912 9 comments 16 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: waiting-for-triage
Dominant language
Java
Stars
9.5k
Forks
2.9k
Avg merge
1d 7h
Merged PRs (30d)
6

Description

Expected Behavior

Developers should be able to register multiple MCP servers on non-default paths, and these paths could be parametrized in a way similar to how it's done in normal controllers with @PathVariable, or something similar in functionality.

Current Behavior

Only a single MCP server can be hosted in the app, and its path cannot be parametrized.

Context

There are tools, such as https://zapier.com/ , which seemingly allow creating customized MCP servers, with only some of their integrations available as tools.

This is also similar to how https://atlassian.com/rovo allows creating multiple agents (that is more A2A specific though) with limited sets of tools.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by tracing how Spring AI currently registers its single MCP server and resolves its path, then compare the requested behavior with existing controller path-variable support. Done means multiple MCP servers can be registered on non-default, parameterized paths with coverage for the supported routing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.