Feature Request: Allow Custom Alias for MCP Server project_id in API URLs

[flefevre]

Description

Hello 👋

First of all, thank you for the amazing work on Langflow!

I'm using the MCP server to integrate multiple Langflow projects into external tools. Currently, each project is accessed via a URL such as:

http://LANGFLOW_SERVER_ADDRESS/api/v1/mcp/project/PROJECT_ID/sse

However, the PROJECT_ID is a non-human-readable identifier (likely a UUID), which makes it difficult to know what each MCP server is doing — especially when managing several running flows.

Problem

External tools (e.g. webhooks, pipelines, integrations) often treat the PROJECT_ID as a meaningful part of the endpoint — essentially as the name of the service. When the project_id is an opaque string, it's hard to tell which MCP is which without consulting a mapping somewhere else.

Proposed Feature

Introduce the ability to define a custom alias for each Langflow project that can be used in place of the project_id in the URL, such as:

http://LANGFLOW_SERVER_ADDRESS/api/v1/mcp/project/support-agent/sse

This would involve:

• Adding an optional alias field to each project.
• Updating the MCP server to resolve either:
  • project_id (default behavior),
  • or a unique alias, when present.
• Aliases would need to be unique across projects to avoid collisions.

Benefits

• Human-readable and meaningful API endpoints.
• Easier integration with external tools that expect service identifiers in the URL.
• Simpler debugging and management of multiple concurrent MCP servers.

Example Use Case

Project Name	Project ID (current)	Proposed Alias	API Endpoint Example
Customer Support	fe1b66f3-d4b7-4f5b-b08e-a8942c3c	support-agent	/api/v1/mcp/project/support-agent/sse
Internal Bot	98e7c52e-c3fd-40e2-9fa7-8a88b1cf	internal-assistant	/api/v1/mcp/project/internal-assistant/sse

---

Let me know if this sounds feasible — happy to help discuss or test this feature 🙌

Thanks again for Langflow!