mcpbeat Sign in

Convex Quickstart Agent Skill

Initializes a new Convex project from scratch or adds Convex to an existing app. Use this skill when starting a new project with Convex, scaffolding with npm create convex@latest, adding Convex to an existing React, Next.js, Vue, Svelte, or other frontend, wiring up ConvexProvider, configuring environment variables for the deployment URL, or running npx convex dev for the first time, even if the user just says "set up Convex" or "add a backend."

3k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
12308
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/get-convex/convex-backend --skill convex-quickstart

What comes with it

912 bytes besides the instruction
agents/openai.yaml
assets/icon.svg

The instruction itself

24 sections, as written by the author

Convex Quickstart

Set up a working Convex project as fast as possible.

When to Use

  • Starting a brand new project with Convex
  • Adding Convex to an existing React, Next.js, Vue, Svelte, or other app
  • Scaffolding a Convex app for prototyping

When Not to Use

  • The project already has Convex installed and convex/ exists - just start

building

  • You only need to add auth to an existing Convex app - use the

convex-setup-auth skill

Workflow

  • Determine the starting point: new project or existing app
  • If new project, pick a template and scaffold with npm create convex@latest
  • If existing app, install convex and wire up the provider
  • Run npx convex dev to connect a deployment and start the dev loop
  • Verify the setup works

Use the official scaffolding tool. It creates a complete project with the

frontend framework, Convex backend, and all config wired together.

Pick a template

| Template | Stack |

| -------------------------- | ----------------------------------------- |

| react-vite-shadcn | React + Vite + Tailwind + shadcn/ui |

| nextjs-shadcn | Next.js App Router + Tailwind + shadcn/ui |

| react-vite-clerk-shadcn | React + Vite + Clerk auth + shadcn/ui |

| nextjs-clerk | Next.js + Clerk auth |

| nextjs-convexauth-shadcn | Next.js + Convex Auth + shadcn/ui |

| nextjs-lucia-shadcn | Next.js + Lucia auth + shadcn/ui |

| bare | Convex backend only, no frontend |

If the user has not specified a preference, default to react-vite-shadcn for

simple apps or nextjs-shadcn for apps that need SSR or API routes.

You can also use any GitHub repo as a template:

npm create convex@latest my-app -- -t owner/repo
npm create convex@latest my-app -- -t owner/repo#branch

Scaffold the project

Always pass the project name and template flag to avoid interactive prompts:

npm create convex@latest my-app -- -t react-vite-shadcn
cd my-app
npm install

The scaffolding tool creates files but does not run npm install, so you must

run it yourself.

To scaffold in the current directory (if it is empty):

npm create convex@latest . -- -t react-vite-shadcn
npm install

Start the dev loop

npx convex dev is a long-running watcher process that syncs backend code to a

Convex deployment on every save. It also requires authentication on first run

(browser-based OAuth). Both of these make it unsuitable for an agent to run

directly.

Ask the user to run this themselves:

Tell the user to run npx convex dev in their terminal. On first run it will

prompt them to log in or develop anonymously. Once running, it will:

  • Create a Convex project and dev deployment
  • Write the deployment URL to .env.local
  • Create the convex/ directory with generated types
  • Watch for changes and sync continuously

The user should keep npx convex dev running in the background while you work

on code. The watcher will automatically pick up any files you create or edit in

convex/.

Exception - cloud or headless agents: Environments that cannot open a

browser for interactive login should use Agent Mode (see below) to run

anonymously without user interaction.

Start the frontend

The user should also run the frontend dev server in a separate terminal:

npm run dev

Vite apps serve on http://localhost:5173, Next.js on http://localhost:3000.

What you get

After scaffolding, the project structure looks like:

my-app/
  convex/           # Backend functions and schema
    _generated/     # Auto-generated types (check this into git)
    schema.ts       # Database schema (if template includes one)
  src/              # Frontend code (or app/ for Next.js)
  package.json
  .env.local        # CONVEX_URL / VITE_CONVEX_URL / NEXT_PUBLIC_CONVEX_URL

The template already has:

  • ConvexProvider wired into the app root
  • Correct env var names for the framework
  • Tailwind and shadcn/ui ready (for shadcn templates)
  • Auth provider configured (for auth templates)

Proceed to adding schema, functions, and UI.

Path 2: Add Convex to an Existing App

Use this when the user already has a frontend project and wants to add Convex as

the backend.

Install

npm install convex

Initialize and start dev loop

Ask the user to run npx convex dev in their terminal. This handles login,

creates the convex/ directory, writes the deployment URL to .env.local, and

starts the file watcher. See the notes in Path 1 about why the agent should not

run this directly.

Wire up the provider

The Convex client must wrap the app at the root. The setup varies by framework.

Create the ConvexReactClient at module scope, not inside a component:

// Bad: re-creates the client on every render
function App() {
  const convex = new ConvexReactClient(
    import.meta.env.VITE_CONVEX_URL as string,
  );
  return <ConvexProvider client={convex}>...</ConvexProvider>;
}

// Good: created once at module scope
const convex = new ConvexReactClient(import.meta.env.VITE_CONVEX_URL as string);
function App() {
  return <ConvexProvider client={convex}>...</ConvexProvider>;
}
React (Vite)
// src/main.tsx
import { StrictMode } from "react";
import { createRoot } from "react-dom/client";
import { ConvexProvider, ConvexReactClient } from "convex/react";
import App from "./App";

const convex = new ConvexReactClient(import.meta.env.VITE_CONVEX_URL as string);

createRoot(document.getElementById("root")!).render(
  <StrictMode>
    <ConvexProvider client={convex}>
      <App />
    </ConvexProvider>
  </StrictMode>,
);
Next.js (App Router)
// app/ConvexClientProvider.tsx
"use client";

import { ConvexProvider, ConvexReactClient } from "convex/react";
import { ReactNode } from "react";

const convex = new ConvexReactClient(process.env.NEXT_PUBLIC_CONVEX_URL!);

export function ConvexClientProvider({ children }: { children: ReactNode }) {
  return <ConvexProvider client={convex}>{children}</ConvexProvider>;
}
// app/layout.tsx
import { ConvexClientProvider } from "./ConvexClientProvider";

export default function RootLayout({
  children,
}: {
  children: React.ReactNode;
}) {
  return (
    <html lang="en">
      <body>
        <ConvexClientProvider>{children}</ConvexClientProvider>
      </body>
    </html>
  );
}
Other frameworks

For Vue, Svelte, React Native, TanStack Start, Remix, and others, follow the

matching quickstart guide:

Environment variables

The env var name depends on the framework:

| Framework | Variable |

| ------------ | ------------------------ |

| Vite | VITE_CONVEX_URL |

| Next.js | NEXT_PUBLIC_CONVEX_URL |

| Remix | CONVEX_URL |

| React Native | EXPO_PUBLIC_CONVEX_URL |

npx convex dev writes the correct variable to .env.local automatically.

Agent Mode (Cloud and Headless Agents)

When running in a cloud or headless agent environment where interactive browser

login is not possible, set CONVEX_AGENT_MODE=anonymous to use a local

anonymous deployment.

Add CONVEX_AGENT_MODE=anonymous to .env.local, or set it inline:

CONVEX_AGENT_MODE=anonymous npx convex dev

This runs a local Convex backend on the VM without requiring authentication, and

avoids conflicting with the user's personal dev deployment.

Verify the Setup

After setup, confirm everything is working:

  • The user confirms npx convex dev is running without errors
  • The convex/_generated/ directory exists and has api.ts and server.ts
  • .env.local contains the deployment URL

Writing Your First Function

Once the project is set up, create a schema and a query to verify the full loop

works.

convex/schema.ts:

import { defineSchema, defineTable } from "convex/server";
import { v } from "convex/values";

export default defineSchema({
  tasks: defineTable({
    text: v.string(),
    completed: v.boolean(),
  }),
});

convex/tasks.ts:

import { query, mutation } from "./_generated/server";
import { v } from "convex/values";

export const list = query({
  args: {},
  handler: async (ctx) => {
    return await ctx.db.query("tasks").collect();
  },
});

export const create = mutation({
  args: { text: v.string() },
  handler: async (ctx, args) => {
    await ctx.db.insert("tasks", { text: args.text, completed: false });
  },
});

Use in a React component (adjust the import path based on your file location

relative to convex/):

import { useQuery, useMutation } from "convex/react";
import { api } from "../convex/_generated/api";

function Tasks() {
  const tasks = useQuery(api.tasks.list);
  const create = useMutation(api.tasks.create);

  return (
    <div>
      <button onClick={() => create({ text: "New task" })}>Add</button>
      {tasks?.map((t) => (
        <div key={t._id}>{t.text}</div>
      ))}
    </div>
  );
}

Development vs Production

Always use npx convex dev during development. It runs against your personal

dev deployment and syncs code on save.

When ready to ship, deploy to production:

npx convex deploy

This pushes to the production deployment, which is separate from dev. Do not use

deploy during development.

Next Steps

  • Add authentication: use the convex-setup-auth skill
  • Design your schema: see

Schema docs

  • Build components: use the convex-create-component skill
  • Plan a migration: use the convex-migration-helper skill
  • Add file storage: see

File Storage docs

Checklist

  • [ ] Determined starting point: new project or existing app
  • [ ] If new project: scaffolded with npm create convex@latest using

appropriate template

  • [ ] If existing app: installed convex and wired up the provider
  • [ ] User has npx convex dev running and connected to a deployment
  • [ ] convex/_generated/ directory exists with types
  • [ ] .env.local has the deployment URL
  • [ ] Verified a basic query/mutation round-trip works

Other skills for the same job

different authors, same section of the catalogue
MCP Builder
by anthropics
vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

30k tokens scripts
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
MCP Builder
by JayZeeDesign
×7

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

37k tokens scripts
Vercel React Native Skills
by vercel-labs
vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens
Vercel React Best Practices
by ratacat
×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

34k tokens
Next Best Practices
by vercel-labs
vendor ×4

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

20k tokens
Using Git Worktrees
by ZhanlinCui
×4

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take get-convex/convex-backend-.agents-convex-quickstart from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npm, npx. Without those the skill loads but fails at the first command.