The API Protocol
AI Actually Understands

One URL. Zero config. Instant AI integration.

Self-Documenting LLM-Native Zero Setup

Give AI a URL, Get Things Done

No SDKs. No documentation portals. No complex auth flows. Just a URL that explains itself.

01

How It Works

1

Get Your URL

berrry.app/api/nomcp/your_token/

Your token encodes permissions directly in the URL

2

AI Reads the Docs

The URL returns HTML that describes every available endpoint, parameter, and example

3

AI Takes Action

Create apps, push updates, read files - all through simple REST calls

02

NOMCP vs Traditional MCP

Model Context Protocol

  1. Install SDK package
  2. Start local MCP server
  3. Configure JSON-RPC transport
  4. Parse capability schema
  5. Negotiate features
  6. Finally make tool calls
6 steps of friction

NOMCP

  1. Give AI the URL
  2. Done
Just works
03

API Reference

GET /apps List your apps
curl "https://berrry.app/api/nomcp/{token}/apps?limit=10"
POST /apps Create an app
From Files Remix
{
  "subdomain": "my-app",
  "title": "My App",
  "files": [
    {"name": "index.html", "content": "..."}
  ]
}
PUT /apps/{subdomain} Push new version
{
  "files": [{"name": "index.html", "content": "..."}],
  "message": "Fixed the bug"
}

Unchanged files are preserved automatically

GET /apps/{subdomain}/files/{name} Read file content
?offset=10&limit=10Line range
?search=TODO&context=2Grep mode
04

Token Scopes

brry_rw_xxx

Read/Write

Full access to create, update, and read apps

brry_ro_xxx

Read Only

List and read apps, no modifications

Tokens can be app-scoped for CI/CD pipelines

05

Try It Live

// Enter your token and click a button to see results
06

Use with Claude

Create a todo app using this API:
https://berrry.app/api/nomcp/brry_rw_xxx/

I'll fetch the API documentation and create your todo app...

Claude reads the service doc, understands the endpoints, and builds your app. No plugins. No configuration.