Paste the API docs instead
Build-along · ~12 min at your own keyboard
For services without a good MCP (or with a bloated one), there's a leaner move: paste the API documentation into context and let Claude write direct calls. Many docs pages ship a 'copy for LLM' button now. It costs context only when you use it, but you now maintain the code: if the API changes, your call breaks. Compare both costs, not just tokens.
The long version: Using API docs instead of MCP ↗
Mac: Mac: use curl or python3 for the call.
Windows: Windows: PowerShell curl is an alias for a different command. Use curl.exe or Invoke-RestMethod, or let Claude write a Python script.
Do this
0/4Checkpoints
- ▸You should now see the docs page for the endpoints you need.
- ▸You should now see a real call return data.
- ▸You should now see your key read from .env, not typed in the chat.
The three ways this goes wrong
- The call fails with 401 or 403. — Check the key name and the auth header in the docs. Confirm the key is valid in the service's dashboard.
- You pasted the whole manual. — Paste only the endpoints you need. Less context, fewer errors.
- Rate limit error. — Wait a minute, then retry with fewer calls. Check the limits in the docs.
Share what happened
Paste which API, what the call returned (trimmed), and your one-line MCP-vs-docs verdict for this service.
Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].
🔒 Don't paste confidential, personal-health, or payment info.