Wire Amdahl into your agents.
Connect your data, paste your API key. Your agent takes it from there.
Connect in the Claude web app or Claude Desktop
- Open Claude and go to Settings → Connectors.
- Click Add → Add custom connector.
- Name it Amdahl and set the URL to
https://app.amdahl.ai/mcp. - Click Connect, then Configure.
- Sign in to Amdahl when prompted, then choose this workspace.
Need a config-file or CLI path instead?
- Generate an API key.
- Copy and paste the snippet below into the client of your choice:
Add to your Claude Desktop config and restart.
{
"mcpServers": {
"amdahl": {
"url": "https://app.amdahl.ai/mcp",
"headers": {
"X-API-Key": "amdhl_YOUR_API_KEY_HERE"
}
}
}
}Building a custom agent instead of an MCP client?
Secure by default.
Every connection is authenticated, every call is logged, every customer’s data sits in its own isolated tenancy. Same posture across MCP and REST.
SOC 2 Type 2 certified
Audited for security, availability, and confidentiality. Per-customer isolation at the database layer.
Encryption in transit and at rest
TLS 1.2+ in transit, AES-256 at rest. Zero retention with every LLM provider we query.
Scoped, revocable API keys
One key per agent, scoped to the tools it needs, revoked the moment a teammate leaves. Read-only by default.
No training on customer data
Your conversations never train a model. Answers stay grounded in your data; the data stays yours.
MCP semantics, plain English
Tool responses go to the runtime you chose (your Claude, Cursor, or custom client) and nowhere else. Rate limits, audit logs, and observability ship by default.
Agents that search and score in production.
Score outbound before it sends
The SDR agent pastes the opener. Amdahl searches the objections that killed similar deals, then scores the draft against them. Thin evidence never ships.
amdahl.evals({ action: "run", inputs: { message: opener, artifact_type: "outreach" } })Search buyer language for today's draft
A cron pulls the language customers used this month, then scores the morning LinkedIn draft against it. Every mark links back to the source call.
amdahl.search({ action: "query", query: "buyer language for today's POV" })Pull churn signal, then score the outreach
Queries what at-risk accounts actually said this month, then scores the retention draft against it.
amdahl.search({ action: "query", query: "churn signals this month", mode: "semantic", audience: "customer_voice", hydrate: true })Battle card claim scored in Cursor
An engineer pastes a competitive claim. The MCP pulls what buyers said about that competitor, then returns a score and cited wins.
amdahl.evals({ action: "run", inputs: { message: claim, artifact_type: "objection_response" } })