Domains
An MCP integration has two different destinations. AI clients connect to your MCP endpoint, while Mitu sends tool calls to the API base URL configured for your existing backend. Keeping those two addresses separate lets you provide a dedicated MCP hostname without changing the API that already powers your product.
For example, customers might connect to https://mcp.yourdomain.com/mcp, while the corresponding tool requests are sent to operations beneath https://api.yourdomain.com.
API base URL
Configure the HTTPS base URL for the API that already powers your product.
Endpoint paths are resolved relative to this base URL. If you register POST /orders, Mitu sends the corresponding request to the /orders operation on the configured API host.
You do not provide Mitu with your application’s own API credential simply to authenticate these forwarded requests. When Mitu sends a request to your backend, your application verifies that it came through Mitu using the signing secret issued for your integration.
If a tool requires a signed-in customer and OAuth is being used, the customer’s access token can also be forwarded so your existing customer authentication and authorisation rules continue to apply.
See Request verification and MCP authentication for these two separate concerns.
MCP URL
The MCP URL is the address compatible AI clients connect to. By default, you can use the Mitu-provided endpoint for your integration. You can also configure a custom MCP hostname so customers connect through a domain associated with your own product.
Changing the MCP hostname does not change the API base URL used by your backend. The custom domain is the client-facing MCP entry point, while your existing API continues receiving the corresponding requests behind it.
Configure a custom domain
Add your hostname
Open the domain configuration for your MCP integration and enter the hostname you want customers to use, such as mcp.yourdomain.com.
Add the DNS records
Create the DNS records shown by Mitu using your DNS provider. Enter the values exactly as provided so ownership and routing can be verified correctly.
Verify the domain
Verify ownership after the DNS records have propagated. If the records are not visible yet, you can retry verification later without changing the rest of your MCP configuration.
Keep the two domains separate
The MCP domain and API domain serve different purposes and do not need to match. A customer-facing MCP endpoint such as mcp.example.com can forward operations to an existing API at api.example.com, and your backend does not need to be moved or renamed to support the custom MCP domain.
This separation lets you introduce an AI-agent channel alongside your existing clients without changing the URL structure those clients already use.