API & MCP: manage your account from Claude Code and OpenAI
Create a key, connect to the MCP server; list projects, start builds, edit data and images — without opening the console.
DevAny has an MCP (Model Context Protocol) server and its REST twin. Claude Code, OpenAI's Responses API or any HTTP client use the same tool set: projects, builds, publishing, records, images, checks and — for admin accounts — platform settings.
A key acts as your account and is limited to the scopes you grant. The build scope can spend credit; content edits are free and live at once.
Connect
- 1Create a key
Settings → API & MCP. Name it, pick scopes, optionally set an expiry. The key is shown once.
- 2Claude Code
Paste the ready command: claude mcp add --transport http devany https://devany.ai/api/mcp --header "Authorization: Bearer dk_…"
- 3OpenAI
In the Responses API add it as a type:'mcp' tool with the same url and Authorization header; for Custom GPT Actions import the /api/v1/openapi document.
- 4First call
capabilities: version, recent changes and the tools your key can see.
OpenAI Responses API
{
"model": "gpt-5",
"tools": [{
"type": "mcp",
"server_label": "devany",
"server_url": "https://devany.ai/api/mcp",
"headers": { "Authorization": "Bearer dk_…" },
"require_approval": "never"
}],
"input": "List my projects and run a polish check on the first one."
}REST twin (curl)
curl -s https://devany.ai/api/v1/tools/list_projects \
-H "Authorization: Bearer dk_…" -H "content-type: application/json" -d '{}'Every tool is POST /api/v1/tools/{name}; the body is the tool's input schema.
Scopes
| What it allows | Spends credit | |
|---|---|---|
| projects:read | List, settings, build status, checks | |
| projects:write | Create, configure, publish, delete | |
| build | Generation, edits, repair, Creative Lab | |
| data | Records, fields, images, app users | |
| billing:read | AI Credit balance | |
| admin | Platform settings and commercial center (admins only) |
ChatGPT's custom connectors currently want OAuth; DevAny uses keys. The Responses API, the Agents SDK and Custom GPT Actions (OpenAPI + API key) work directly.
Revoke it in Settings; every tool using it fails immediately. At most 10 live keys per account, optionally with an expiry.
When the admin console requires a WARP identity (admin.access_required) a key cannot pass; turn the setting off or use the console.
Key takeaways
- One key = your account, with the scopes you chose.
- Claude Code and OpenAI connect to the same MCP server; the REST twin serves any HTTP client.
- capabilities → api_catalog → api_request: a path exists even without a curated tool.
Related topics
Still stuck? Ask the assistant in the corner, or browse the FAQ.