Connect an AI assistant through MCP
Give a compatible AI client access to your Titan workspace using a personal API key.
MCP lets an external AI assistant use Titan tools to inspect your workspace and perform permitted actions. Use it to prepare resources, create run setups and queues, and author strategy content when your account has authoring permission.
Before you connect
You need:
- Active Titan access.
- A personal Titan API key.
- An AI client that supports remote Streamable HTTP MCP and a bearer-token credential or custom Authorization header.
- The exact Titan MCP server URL supplied with your workspace access. Ask your Titan administrator for it if it has not been provided.
Use the supplied endpoint ending in /mcp. The browser dashboard address is not a substitute for the MCP endpoint.
Configure the connection
Open your AI client's MCP or external-tool settings and add a server with these values:
| Field | Value |
|---|---|
| Name | Titan |
| Transport | Streamable HTTP / remote HTTP MCP |
| Server URL | The exact Titan MCP URL supplied for your workspace |
| Authorization | Bearer token using your personal Titan API key |
If the client asks for an HTTP header instead of a token field, the header name is Authorization and its value is Bearer followed by the key. Store the secret in the client's credential setting rather than in ordinary chat.
This connection uses a personal API key. A client that only supports automatic OAuth discovery cannot use this setup method without support for the bearer credential.
Verify with a read-only request
After the client loads the tool list, ask:
Show the devices and strategies available in my Titan workspace. Report their names, IDs, and current status. Do not create, update, start, or delete anything, and do not display credentials.
Confirm that the returned records belong to the intended workspace. If the key is invalid or revoked, reconnect with a valid key. If an operation is forbidden, check account access and the permission required by that operation.
Prepare and execute work
Be explicit about preparation and execution:
Inspect the requirements for this strategy and prepare a one-item queue using my chosen device, adapter, and resources. Show the exact selections and any missing fields. Stop at Ready until I ask you to start.
Tool names and available operations come from the connected Titan server. Let the assistant use the current tool definitions instead of copying arguments from an old example.
If a write times out, have the assistant read the resulting record before repeating it. For a rate-limit response, wait for the reported retry interval. Repeated immediate retries do not repair an authorization or validation problem.
Continue with Your first automation or Authoring automations.