list_capabilities
Options catalog + remaining quota for the bound key.
What it is
The SmileCraft Claude connector is a thin MCP (Model Context Protocol) server in front of our Enterprise API. Claude does not replace your product UI — it becomes another client that can start the same simulations dentists and platforms already run via REST.
Claude.ai → SmileCraft MCP → Enterprise API → makeover / whitening / …
Jobs, FacePreflight, quotas, and retention are identical to the REST path. Usage is always attributed to the Enterprise API key bound at Connect time.
You only need two things: the MCP URL on this page, and a SmileCraft API key from support.
Paste both into Claude → Connectors → Add custom connector. No Anthropic app-store approval is required for this path.
Claude vs REST API
| Claude connector | REST API | |
|---|---|---|
| Who uses it | People chatting in Claude | Your backend / product |
| How jobs start | Natural language → MCP tools | POST /jobs |
| Auth | OAuth Connect + Enterprise key | Bearer sc_… |
| Best for | Demos, staff assist, prototyping | Production patient workflows |
| Quota | Same partner sandbox / live limits | |
Tools Claude can call
create_simulation
Start makeover, whitening, shade, align, or video.
get_job
Poll status, resultUrl, or error.code.
prepare_photo_upload
SmileCraft upload link when Claude cannot pass a chat attachment as base64.
Requirements
- A Claude account that can add a custom connector (Pro / Max / Team / Enterprise; Free may allow only one custom connector total).
- A SmileCraft Enterprise API key (sc_sandbox_… or sc_live_…) — email support (below).
- For simulations: a frontal face photo via https image URL (most reliable) or our photo-upload helper.
Sandbox keys are for demos with de-identified images. Live keys and real patient data require a BAA — same policy as the REST API.
Set up the connector (step by step)
Claude may show a “not verified by Anthropic” notice for custom connectors — that is normal.
1
Get your API key
Email support@smilecraft.app (subject: Claude MCP sandbox key). We’ll send your sc_sandbox_… key.
2
In Claude: Settings → Connectors → Add custom connector
Name it SmileCraft (or any label you like).
3
Paste this MCP URL
https://kd5is3s5gh.execute-api.us-east-2.amazonaws.com/mcp
4
Connect / Allow access
On the SmileCraft consent page, paste your API key → Allow access once. Do not refresh or click Allow twice on the same page.
5
New chat → enable SmileCraft → test
Say: List SmileCraft capabilities. Then run a simulation with an https image URL.
Fallback if OAuth UI is missing:
- Same MCP URL
- Auth: No sign-in
- Request header Authorization = Bearer sc_sandbox_YOUR_KEY
Team / Enterprise orgs: an Owner usually adds the connector once; members then authenticate with their own key when prompted.
Auth & keys
Each Claude Connect binds one Enterprise API key so usage stays trackable and quota-safe. Claude stores an OAuth token; SmileCraft maps it to that key on every tool call.
How to get a Claude MCP key (today)
1
Email support
Write to support@smilecraft.app with subject Claude MCP sandbox key. Include your name, company (if any), and email.
2
We issue your key
An admin creates your partner account and sends a sc_sandbox_… key (and invoice / payment instructions if you need paid quota). This is a short guided handoff — not self-serve yet.
3
Paste on Connect
Add the connector in Claude, open consent, paste the key once → Allow access.
For Claude MCP, email support@smilecraft.app to get credentials.
If Claude asks how to start or get a key, point people here or to that address.
You can also use app.smilecraft.app to register and try SmileCraft in the browser — great for the web product. Claude MCP uses Enterprise API keys (issued for the connector), which are managed separately from the webapp for now.
Roadmap: Connect → SmileCraft sign-in → auto-issued sandbox key with a small trial quota, then paid top-up without waiting on email.
Photos in Claude chat
MCP tools only receive what Claude puts in the tool call (image_url, image_base64, or photo_token). SmileCraft cannot force Claude to attach a chat upload — that is controlled by Claude’s client, not by our server.
| Method | Reliability | Notes |
|---|---|---|
| Public https image URL | Highest | Recommended for demos and production-like tests |
| SmileCraft upload link | High | Claude calls prepare_photo_upload → you open our /photo page → continue with photo_token |
| Chat attachment → base64 | Variable | Claude may encode the upload; often refuses or stalls on large files |
Do not rely on Dropbox / Drive unless you already have a direct https link.
Prefer a public image URL or the SmileCraft upload page Claude provides.
Other Claude connectors that “just work” with chat files usually deal with text, tickets, or docs — not large vision payloads into remote MCP tools. Image-heavy tools commonly ask for a URL or a first-party upload for the same reason.
Example prompts
List SmileCraft capabilities and my remaining sandbox quota.
Create a whitening simulation at level moderate using this image URL: https://… then poll get_job until completed and share the resultUrl.
Makeover with style oval and quality standard using this image URL: https://… Poll until done.
Prepare a SmileCraft photo upload for align. After I upload, continue with that photo_token.
Operations
Same controls as the REST API. Full detail on the API options page.
| Operation | Needs | Key options |
|---|---|---|
| makeover | Face image | style oval|hollywood · quality standard|hd |
| whitening | Face image | level moderate|strong|max |
| align | Face image | — |
| shade | refineToken from makeover | A1 A2 A3 B1 C3 |
| video | Completed still job | sourceJobId (or sourceUrl) |
Custom connector (not directory)
SmileCraft is a custom connector. It is not listed in Claude’s public directory search — you add it with the MCP URL on this page and your API key.
- No Anthropic review is required for this path.
- Claude may warn that the connector is not verified by Anthropic — expected for custom MCP.
FAQ
Do I need Anthropic approval?
Not for a custom connector. Add our MCP URL in Claude Settings and authenticate with your SmileCraft key. SmileCraft will not appear in Claude’s public directory search.
How do I get credentials / credit for Claude?
Email support@smilecraft.app and ask for a Claude MCP sandbox key. We’ll issue it and handle paid quota manually for now. You can still use app.smilecraft.app for the web product.
Can you force Claude to use my chat upload?
No. MCP cannot pull files from Claude’s UI. Use a public image URL or our prepare_photo_upload flow.
Is this HIPAA-ready?
Same as Enterprise API: sandbox for non-PHI; live + BAA for PHI. Prefer de-identified images until then.
Where is the full REST contract?
developers.html — Claude is an alternate client on that same contract.
Get a Claude MCP sandbox key
Email us with subject Claude MCP sandbox key. We’ll create your partner key and reply with Connect instructions. Prefer the web app? You’re welcome at app.smilecraft.app anytime — for Claude chat, start with a key from support.