Skip to main content

Use your own services in an assistant

Section: DOC-IN-tools-connections-custom-mcp-feature#custom-mcp-servers.

Your assistant needs information from a service you already run or pay for. Connect that service through a supported MCP server so Travila can call its selected tools during the conversation. Keep its credential in the secret store and put only the secret's name in the server configuration.

For a complete example, build an assistant that reads a website using your Firecrawl account. The same registration pattern works for a compatible server exposing your own application operations.

Take a question from setup to a verified answer​

Section: DOC-IN-tools-connections-custom-mcp-feature#setup.

  1. Choose a question your service can answer and a test record or page you can inspect yourself.
  2. Store the service credential and register its public HTTPS MCP endpoint.
  3. Test the saved connection and inspect the returned tools. Select only those needed for the task.
  4. Enable the server for the intended conversation or agent, then ask the test question.
  5. Inspect the actual tool result and check the answer against your source.

The finished integration produces a supported answer from the selected service. Registration or a successful connection test alone is not the finished customer experience. Follow the worked recipe for requests and recovery steps.

Choose the right connection for your application​

Section: DOC-IN-tools-connections-custom-mcp-feature#scope-and-current-limitations.

A custom MCP server must be publicly reachable over HTTPS with a supported MCP-over-HTTP transport. If only your application can reach the system, use a client tool instead.

Current public configuration uses the tenant's default project. A different project identifier does not create a separate test environment or customer boundary; use a separately provisioned tenant where separation is required.

Choose a service you trust with the task's arguments and a credential limited to the intended work. Configure tool approval before offering sensitive changes. Being able to connect to a service does not grant permission for every action it exposes.

Maintain the connection after launch​

Section: DOC-IN-tools-connections-custom-mcp-feature#available-operations.

When the service changes or a credential expires, use the maintenance steps to inspect dependencies, update the full saved configuration and verify another real call. For urgent revocation, revoke the credential at its issuer; a configuration update does not recall calls already in progress.

Exact fields and limits belong in the custom server reference and secret reference. Use them when you need the full request and response fields for a maintenance operation.

Section: DOC-IN-tools-connections-custom-mcp-feature#related.

Document ID: DOC-IN-tools-connections-custom-mcp-feature. Section identities and revisions.