[Feature]: Allow to specify the FastMCP mount_path attribute

[XtratusCloud]

Is your feature request related to a problem? Please describe.

To allow the MCP server to be configured under an endpoint with path, the mount_path parameter must be assigned when instantiating FastMCP.

This attribute was incorporated in v1.8.0 of python-sdk, PR #540

Describe the solution you'd like

Add a new setting that can be configured at run time by means of an env variable or run argument, and assign the value to the FastMCP. Default value is “/”.

Describe alternatives you've considered

No response

Use Case

No response

Additional Context

No response

[sooperset]

Hi @XtratusCloud, thanks for the request! However, mount_path isn't necessary for mcp-atlassian since it's designed as a single integrated server that handles both Jira and Confluence together.

The mount_path parameter is intended for mounting multiple separate MCP servers at different paths in an ASGI application, but mcp-atlassian already combines everything into one server.

If you need to run the server at a custom path, you can use the existing --path option:

mcp-atlassian --path /custom/path

[psychoNarc]

Hi @sooperset ,

Can you please guide me on how to invoke tools defined in the MCP server directly from MCP client as endpoints to which the requests from MCP client can be posted.

eg:

To call the tool confluence_search in MCP server from MCP client, I can use endpoint: http://<base_url_server>:/mcp/confluence/confluence_search.

I am unable to find a solution to this and currently calling the tools using self.client.call_too(tool_name,arguments=<payload_json>)