GoLocomotiveConnect your AI
Your app as an MCP server. The AI you already use reads and changes your data as you, under the same rules as the screens.
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, creates a ticket, 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. Your app can act as an MCP server. Your assistant is the client.
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.
Three promises#
- It acts as you. The assistant signs in with your account. It sees what you see and can do what you can do, nothing more. An account that cannot delete an order on a screen cannot delete it through the assistant either.
- 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 to the AI. A rule can refuse an AI an action that a person can do on a screen, for example "an AI never deletes a payment". See 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 connect your assistant: Set up your AI client.
What has been tested#
- Claude Code (Anthropic's coding assistant) 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.
- claude.ai, the Claude desktop app and ChatGPT connect through that same sign in flow. They need the app's public address, and no live app has been connected to them yet. Until then, treat them as the next step, not a tested path.
Not there yet#
- Files: the assistant cannot upload or download a file field. 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. An account protected by a second step signs in to the app first, then returns to the assistant's sign in.