Connect your AI agent to Fast Track AI

Fast Track AI is available over MCP. Your MCP client connects to a single Fast Track endpoint and gets the whole Fast Track agent behind one tool, rather than an integration per feature.
You sign in through your browser with your normal Fast Track account. There are no API keys to issue, store or rotate, and no service user to manage. Every request runs as the person who signed in, with their role and their permissions.

Before you start

You need three things:
  1. The integration enabled for your brand. It is off until we switch it on. Ask your partner manager if you are not sure.
  2. Your Fast Track host. The same address you use for Fast Track today, for example yourcompany.ft-crm.com. This document writes it as <your-host>.
  3. An MCP client that supports OAuth in the browser. Claude Code is the client we have verified end to end, and the steps below use it.

Your endpoint

https://<your-host>/llm-agent/mcp
Authentication is OAuth 2.1 with dynamic client registration, so a compliant client discovers everything it needs from that URL. There is nothing to configure beyond the address.

Set up Claude Code

1. Add the connection
claude mcp add --transport http --scope user fasttrack https://<your-host>/llm-agent/mcp
--scope user makes the connection available in every project. Drop it if you want it only in the current directory.
2. Sign in
Start Claude Code, then run:
/mcp
Select fasttrack and choose Authenticate. Your browser opens on the Fast Track login. Complete it and return to the terminal.
claude mcp list reports connection status but does not start the login, so use /mcp for this step.
3. Check it worked
In the same /mcp view, open fasttrack. You should see one tool, ask.
If the connection says connected but no tool appears, restart Claude Code. Tools are registered when the session starts, so a session that was already open before you signed in will not see them.
4. Optional: raise the client timeout
A single request can run for up to ten minutes. Some clients give up sooner. For Claude Code:
export MCP_TOOL_TIMEOUT=600000

Using it

The connection exposes one tool:
ask(query, conversationId?)
query is a natural language request, the same kind you would type into Fast Track AI directly. The response contains the agent's answer and a conversationId.
Pass that conversationId on your next call to continue the same thread. The agent keeps the earlier context. Omit it to start fresh.
Most clients show the tool prefixed with the name you gave the connection. If you named it fasttrack, Claude Code will show it as mcp__fasttrack__ask. Use whatever your client displays.
In practice you rarely call the tool by name. Ask your assistant for something that needs Fast Track data and it will reach for the tool itself, for example:
List the scheduled jobs configured in Fast Track and tell me which are disabled

What the agent can and cannot do

The agent behind ask is the same one that runs inside Fast Track, with the same capabilities.
Permissions are the important part. The agent acts as the signed-in user, so it is bound by that user's role. Anything that user cannot do in Fast Track, the agent cannot do on their behalf. Connecting over MCP grants no access that the person did not already have.

Limits in this version

  1. No progress updates. A long run returns nothing until it finishes. Plan for a wait rather than a stream.
  2. One request at a time per conversation. A second request against the same conversationId is rejected while the first is still running. Use separate conversations for parallel work.
  3. Ten minute ceiling on a single request.

Troubleshooting

The login loops, or every request returns 401. The integration is most likely not enabled for your brand yet. Contact your partner manager rather than retrying.
The endpoint appears not to exist. Same cause. Until the integration is switched on for your brand, the endpoint is not served.
Connected, but no tool listed. Restart your client. See step 3.
Requests time out at 60 seconds. Your client's own timeout, not ours. See step 4.

Security

The MCP session carries the same trust as a signed-in Fast Track user. Treat it that way:
  1. Sign out or remove the connection when you finish on a shared or temporary machine.
  2. Each person connects with their own account. Do not share one connection across a team.
  3. Access is revoked the same way any Fast Track access is revoked, by changing that user's role or removing the account.

Getting access or help

The integration is enabled per brand on request. To have it switched on, or
This is an early release. If you get stuck, please contact your partner manager. Also, tell us where the setup or the agent falls short, because that feedback shapes what ships to everyone else.