Fix a bug with handling FastAPI root_path parameter

[am1ter]

Describe your changes

Issue resolving

The current version of the library does not handle FastAPI's root_path parameter correctly.

FastAPI.router includes root_path in all its routes by default, so there is no need to add root_path to /messages again, as is done in the current version of fastapi_mcp. The problem is located here.

Because of these duplicated root_path annotations, all requests to the /messages endpoints are processed incorrectly. This issue can be easily reproduced using the following snippet:

from fastapi import FastAPI
from fastapi_mcp import FastApiMCP

app = FastAPI(root_path="/api")  # Does not work, but `app = FastAPI()` works
mcp = FastApiMCP(app)
mcp.mount()

if __name__ == "__main__":
    import uvicorn
    uvicorn.run(app, host="0.0.0.0", port=8101)

When you run MCP Inspector with http://127.0.0.1:8101/mcp connection string you will see the following log in the uvicorn output:

INFO:     Uvicorn running on http://0.0.0.0:8101 (Press CTRL+C to quit)
INFO:     127.0.0.1:53784 - "GET /mcp HTTP/1.1" 200 OK
INFO:     127.0.0.1:60936 - "GET /mcp HTTP/1.1" 200 OK
INFO:     127.0.0.1:60944 - "POST /api/api/mcp/messages/?session_id=a09e48d070204eb09420f54bdeb913ae HTTP/1.1" 404 Not Found

When you run MCP Inspector with http://127.0.0.1:8101/api/mcp connection string you will see the following log in the uvicorn output:

INFO:     Uvicorn running on http://0.0.0.0:8101 (Press CTRL+C to quit)
INFO:     127.0.0.1:32798 - "GET /mcp HTTP/1.1" 200 OK
INFO:     127.0.0.1:32800 - "GET /api/mcp HTTP/1.1" 200 OK
INFO:     127.0.0.1:32802 - "POST /api/api/mcp/messages/?session_id=d52c467095fc4350924b027fd3b578a2 HTTP/1.1" 404 Not Found

This PR fixes this issue.

Tests

This PR introduces some new test to prevent this issue in the future and also it refactors some basic fixtures to enhance flexibility by supporting multiple configurations for test servers.

I think there were a better way to add new tests for this root_path issue, but unfortunately I couldn't find an easy way to resolve a full URL to FastAPI's endpoint. If you can give me an advice how it could be enhanced - please do it and I'll prepare an update.

Issue ticket number and link (if applicable)

N/A

Screenshots of the feature / bugfix

FastAPI's root_path part duplication in the POST request to messages endpoint:

An example of the broken unit tests, that were added in this PR in the case if we do not apply the main changes to fastapi_mcp/server.py (with the changes from this PR all tests are passed correctly).

With the changes from this PR all tests are passed correctly:

Checklist before requesting a review

• Added relevant tests
• Run ruff & mypy (No new errors, but current version of the repository has some errors)
• All tests pass

[jstanden]

I'm having the same issue with FastAPI-MCP in an ECS container behind an AWS load balancer with virtual paths. Everything works fine when removing base_path and just checking router.prefix like this PR.

[jstanden]

In this meantime this seems to work:

mcp_server = FastApiMCP(
    app, 
    include_tags=["mcp"],
    name="MCP Server",
    description="MCP Server Description"
)

mcp_server.mount()

# Add this AFTER mcp mounts
app.root_path = root_path

[paintoxic]

Hey @tori-tadata, this PR is really important when using a root path different from /, because it fixes a critical issue when configuring a FastAPI MCP service to run under a specific prefix path like /prefix. Without this fix, the app may break or behave unexpectedly when it's not mounted at the root.

FYI
@jstanden @ierickson @bfontaine @shaom

[shahar4499]

@am1ter
Great! Thanks for this catch.

I merged it but it's not released yet. For some reason it seems to pass the CI on github, but it breaks the test suite locally.

ERROR tests/test_sse_real_transport.py::test_raw_sse_connection[asyncio-simple_fastapi_app] - AttributeError: Can't get local object 'FastAPI.setup.<locals>.openapi'

Do you mind checking it out?
I opened a revert PR to make sure it's really due to this PR, and it is. When running the test suite on the reverted branch, it works again.

[am1ter]

@shahar4499 Thanks for reporting this!

I've just synced my local environment with the main branch, ran the tests, and all of them passed correctly.
I was able to replicate the error using the following command:

uv run python -c "import multiprocessing; multiprocessing.set_start_method('spawn', force=True); import pytest; pytest.main(['-v', 'tests'])"

The root cause of the issue is that the FastAPI app contains local functions, like the openapi function, which can't be pickled when passed between processes.

As a solution, I changed the fork method we use, and now all tests pass correctly.
PR with the change is available here: #196