GoLocomotiveConnect your AI
You already talk to an AI assistant: Claude, ChatGPT, or a coding tool. GoLocomotive lets that assistant work inside your app. It lists your orders, opens a client, changes a status, as you do on a screen, and under the same rules. The link between the two is MCP, the Model Context Protocol, an open standard that AI assistants use to call tools in other systems.
What it looks like
Which orders of the north site are late this week? Move the ones from regular clients to in progress, and list the others.
The assistant calls your app’s tools: a filtered list of orders, then one update per order. Each update goes through the same checks as a click on a screen. The journal records each change with the mark that an AI made it.
For each kind of record, the app offers five tools: list, view, create, update, delete. Your app’s own actions can be tools too. What your AI can do
Three promises
It acts as you
The assistant signs in with your account. It sees what you see and does what you can do, nothing more.
The AI is yours
You pick the assistant and you pay its provider. GoLocomotive spends no AI on your behalf for this.
Your app can say no
A rule can refuse an AI an action a person can do, for example “an AI never deletes a payment”.
Keep your AI in bounds →
Turn it on
The MCP server is off until your app turns it on. Ask for it in a request: “connect our app to Claude”. The agent turns it on, chooses with you what the assistant can see, and the change goes live with your next deploy.
Then add your app to your assistant. For Claude Code, it is one command with a token from your app:
claude mcp add --transport http orders https://orders.example.com/mcp \
--header "Authorization: Bearer <token>"A connector in a chat app (claude.ai, the Claude desktop app, ChatGPT) uses your app’s own sign in page instead, the standard OAuth flow. Set up your AI client
What has been tested
- Claude Code has worked in an app through its MCP server as a signed in user. The app’s rules and its journal applied to every call.
- The sign in flow that assistants use (OAuth 2.1) works with the official MCP client libraries.
- Not tested yet: claude.ai, the Claude desktop app and ChatGPT. They connect through that same sign in flow, but they need the app’s public address, and no live app has been connected to them yet. Treat them as the next step, not a tested path.
Not there yet
- Files: the assistant cannot upload or download a file. Files go through the app’s screens.
- A page that lists the assistants connected to your account, and a button to revoke one. Today a password change ends every connection.
- A code by email or a second step on the assistant’s sign in page.
Want your AI in your app?
GoLocomotive is in private testing. Access is by invitation. Once you are invited, tell us which assistant your team uses and what it must do in your app.