Warning: May eliminate your entire backend team
KILL YOUR
BOILERPLATE.
You've been writing the same CRUD endpoints for a decade. Upjack ends that. Tell your agent what you want. Get a full MCP server with validation, search, and storage. Automatically.
$ npm i -g @nimblebrain/mpak
$ mpak skill install @nimblebraininc/upjack-app-builder
> Build me a CRM
$ python server.py
// Done. 18 tools. Zero boilerplate.
// .cursor/mcp.json
{
"mcpServers": {
"upjack": {
"command": "npx",
"args": ["@nimblebrain/mpak", "run",
"@nimblebraininc/upjack-app-builder"]
}
}
}
> Build me a CRM
$ python server.py
// windsurf mcp config
{
"mcpServers": {
"upjack": {
"command": "npx",
"args": ["@nimblebrain/mpak", "run",
"@nimblebraininc/upjack-app-builder"]
}
}
}
> Build me a CRM
$ python server.py
847
Lines Killed
per entity
6
Tools Generated
per entity
0
Lines of Code
required
1
Sentence
to build your app
DOSAGE
HOW IT HITS
01
INSTALL THE SKILL
One command. The app-builder skill knows how to generate complete Upjack apps from a description. Schemas, skills, manifest, server. Everything.
npx @nimblebrain/mpak skill install @nimblebraininc/upjack-app-builder02
TELL YOUR AGENT
Describe the app you want in plain English. "Build me a CRM." The agent generates every file: schemas, skills, context, seed data, server entry point.
"Build me a CRM app"03
RUN IT
One command. Full MCP server. Entity management, validation, search, storage. All generated. Zero boilerplate. Zero excuses.
python server.pyCASUALTY REPORT
THINGS UPJACK KILLED
CRUD Endpoints
Auto-generated MCP tools
6 tools per entity. Create, read, update, delete, list, search. You write nothing.
Validation Logic
JSON Schema enforcement
Define constraints once in your schema. Invalid data never hits storage. Ever.
Database Setup
Git-backed JSON storage
Every entity is a file. Every change is a commit. No database to manage.
Search Implementation
Built-in full-text search
Search across all fields with filters. Works the second your schema exists.
Business Logic Code
Markdown skills
Write your expertise in plain English. The AI reads it and acts on it. No functions required.
API Documentation
MCP protocol + resources
Tools are self-describing. Skills are exposed as resources. Documentation writes itself.
BEFORE AND AFTER UPJACK
One entity. The old way needs a model, serializer, viewset, URL config, migrations, tests, and admin registration, spread across 7+ files. Upjack needs one sentence.
The old way / 7+ files 847 lines
# ── models.py ──────────────────────────
class Contact(models.Model):
name = models.CharField(max_length=200)
email = models.EmailField(unique=True)
company = models.CharField(max_length=200, blank=True)
phone = models.CharField(max_length=20, blank=True)
status = models.CharField(
max_length=20,
choices=[('prospect', 'Prospect'),
('qualified', 'Qualified'),
('customer', 'Customer')],
default='prospect'
)
score = models.IntegerField(
validators=[MinValueValidator(0),
MaxValueValidator(100)],
default=0
)
notes = models.TextField(blank=True)
owner = models.ForeignKey(User, on_delete=CASCADE)
created_at = models.DateTimeField(auto_now_add=True)
updated_at = models.DateTimeField(auto_now=True)
class Meta:
ordering = ['-created_at']
# ── serializers.py ─────────────────────
class ContactSerializer(serializers.ModelSerializer):
class Meta:
model = Contact
fields = ['id', 'name', 'email', 'company',
'phone', 'status', 'score', 'notes']
read_only_fields = ['id', 'created_at']
def validate_email(self, value):
if Contact.objects.filter(email=value).exists():
raise serializers.ValidationError(
"Contact with this email already exists"
)
return value
# ── views.py ───────────────────────────
class ContactViewSet(viewsets.ModelViewSet):
queryset = Contact.objects.all()
serializer_class = ContactSerializer
permission_classes = [IsAuthenticated]
filter_backends = [SearchFilter, OrderFilter]
def perform_create(self, serializer):
serializer.save(owner=self.request.user)
@action(detail=False)
def search(self, request):
q = request.query_params.get('q', '')
contacts = self.queryset.filter(
Q(name__icontains=q) |
Q(email__icontains=q) |
Q(company__icontains=q)
)
# ... + urls.py, tests.py, migrations,
# admin.py, permissions, pagination ...
+ urls.py, tests.py, admin.py, migrations ...
Upjack / "Build me a CRM" 1 sentence
# ── Install the skill ──────────────────
$ npx @nimblebrain/mpak skill install @nimblebraininc/upjack-app-builder
# ── Tell your agent ───────────────────
claude > Build me a CRM app
# ── Agent generates ───────────────────
my-crm/
├── manifest.json
├── schemas/
│ ├── contact.schema.json
│ ├── company.schema.json
│ └── deal.schema.json
├── skills/
│ └── lead-qualification/
│ └── SKILL.md
├── context.md
├── seed/
│ └── sample-contacts.json
└── server.py
# ── Run it ────────────────────────────
$ python server.py
# Tools: create_contact, list_contacts,
# search_contacts, ... (18 total)
// Done. You're jacked.
Convinced? One sentence. Zero boilerplate. Ship before standup.
"I SPENT 10 YEARS WRITING CRUD.
THEN I SAID 'BUILD ME A CRM'
AND WENT HOME EARLY."
THEN I SAID 'BUILD ME A CRM'
AND WENT HOME EARLY."
Upjack is for people who are done pretending that writing the same serializer for the 10,000th time is "engineering."
GET
JACKED.
Install the skill. Tell your agent. Ship before standup.
$ npm i -g @nimblebrain/mpak
$ mpak skill install @nimblebraininc/upjack-app-builder
> Build me a CRM
$ python server.py
// Done. 18 tools. Zero boilerplate.
// .cursor/mcp.json
{
"mcpServers": {
"upjack": {
"command": "npx",
"args": ["@nimblebrain/mpak", "run",
"@nimblebraininc/upjack-app-builder"]
}
}
}
> Build me a CRM
$ python server.py
// windsurf mcp config
{
"mcpServers": {
"upjack": {
"command": "npx",
"args": ["@nimblebrain/mpak", "run",
"@nimblebraininc/upjack-app-builder"]
}
}
}
> Build me a CRM
$ python server.py