Integrations
Connect your AI
The short version: HammerThis ships an MCP connector, so the AI you already talk to can drive a real simulation workspace — create and edit models, mesh them, submit solves, and read the results. It signs in as you, spends nothing without asking, and can never walk off with your raw data. Your AI brings the conversation; our solvers bring the physics.
Before you start
You need a HammerThis account whose plan includes the MCP connector. In the desktop workspace, Account menu → Integrations → “Connect your AI” shows your connector URL — and tells you, politely, if your plan doesn’t include it yet.
https://mcp.hammerthis.ai/mcpclaude.ai and Claude Desktop — the two-minute version
OAuth sign-in. No keys to paste, nothing to forget in a dotfile.
- Open Settings → Connectors → Add custom connector and paste the URL above.
- Click Connect. Your browser opens the HammerThis sign-in — your account, your authenticator code. The usual bouncers.
- Read the consent screen — it says exactly which app is asking, what it will be able to do, and what it can’t — then click Approve.
That’s it. The client gets short-lived tokens and refreshes them on its own. Change your mind any time under Account menu → Integrations → Connected apps — Disconnect kills every token that app holds, immediately and without ceremony.
Claude Code
claude mcp add --transport http hammerthis https://mcp.hammerthis.ai/mcp
Claude Code walks you through the same OAuth sign-in. Prefer a key? Append --header "Authorization: Bearer htk_…".
Cursor, VS Code, and other key-based clients
Create a key under Account menu → Integrations → API keys — give it a label, only the scopes it needs, and an expiry. The key is shown exactly once, so put it somewhere sensible on the first try.
{
"mcpServers": {
"hammerthis": {
"url": "https://mcp.hammerthis.ai/mcp",
"headers": { "Authorization": "Bearer htk_…" }
}
}
}
What your AI can do
Build and edit models with typed commands, mesh with the same mesher the desktop uses, run the authoritative preflight check, submit solves and follow them to completion, read result summaries with real units, pull rendered contour images, and hand harder questions to Hardy — our in-platform engineering assistant, who knows the solvers and your result files personally.
Anything consequential — submitting a solve (that spends credits), deleting parts, load cases or projects, clearing loads, stopping a job — is refused by the server until your AI confirms you agreed. Approve is a conversation you have, not a thing that happens to you.
What it cannot do — ever
- Download raw result files or meshes. Summaries, numbers and rendered frames only — your data stays in-house.
- Touch your account, plan, or billing.
- Act without your session or your key. Revoke either and it’s a stranger again.
Scopes — grant only what the client needs
| Scope | What it unlocks |
|---|---|
workspace | Create projects, build and edit models, mesh, preflight |
solve | Submit and stop solves (spends credits — always confirm-gated) |
results | Result summaries, controls, and rendered images |
hardy | Hand questions and tasks to Hardy |
Privacy, in one paragraph
What you type goes to your AI provider under its terms — that conversation is between you two. HammerThis receives only the tool calls your AI sends (commands, settings) and returns engineering results. The connector itself stores nothing between requests. The fine print lives in the privacy policy, and it’s shorter than you’d fear.
Stuck? Write to hello@hammerthis.ai — a human reads it. Or ask Hardy in the app; it has opinions about boundary conditions and is happy to share them.
