Testing phaseThis environment is in pre-launch testing — all data will be reset at launch.
Mockomat
AI INTEGRATION

Mockomat is a prompt.

Tell Claude, Cursor, or any LLM to spin up a mock GraphQL API. They build it, you watch, and the link is in your clipboard before the model finishes its sentence. No login. No config files.

< 60s zero to queryable
10 MCP tools · coming soon
24h guest sessions
0 config files
claude · mockomat-mcp · session
LIVE
— / Three ways in

Pick the entry point that fits your stack.

Whether you're typing a one-liner into ChatGPT or wiring up a long-running Cursor session, there's a path. They all hit the same public API and end with a queryable mock.

01 Easiest

Just ask.

Tell any LLM to use Mockomat.

No tools to install, no API keys to copy. The capability spec at /.well-known/ai-capabilities.md teaches every LLM how to talk to Mockomat. The model spins up a guest project, builds your schema, and hands back a queryable URL. The guest project lasts 24 hours from the start of its guest session and cannot be moved into an account.

"Create a mock GraphQL API for an e-commerce store with products, customers, and orders. Use Mockomat."
02 Coming soon

The MCP server.

Native integration for Claude Desktop, Claude Code, Cursor, Copilot.

mockomat-mcp exposes 10 tools — create_project, list_data_sources, create_table, generate_api, query_data, import_openapi, and more. The session cookie is managed for you. The AI never sees HTTP, just clean tool calls.

# mockomat-mcp — npm package coming soon
03 Migration path

Drop in an OpenAPI spec.

Have a Swagger or OpenAPI file? Mockomat reads it.

Attach a spec to your prompt and the LLM sends it to importOpenApiSpec on the public GraphQL API. Tables, attributes, relations, and default operations — all generated from your existing API contract. Iterate on the model from there.

POST /public-graphql importOpenApiSpec(input: { specContent, selectedSchemas })
— / The wow moment

Watch the AI design,like a movie.

Modelling decisions normally take days of meetings — the PM disagrees with the architect, the dev is in the dark, the tester is waiting for a contract. On Mockomat, the AI builds the schema in real time and your whole team watches the same board. Tables appear. Attributes bind. Relations connect. Everyone sees the same picture, at the same moment.

Product owner sees the data shape stakeholders care about
Architect reviews relations + cardinalities live
Developer starts queries against the mock instantly
Tester pins fixtures the moment they appear
LIVE · Modelling Board
PO AR DV QA
+ Claude
User
· email · fullName · avatarUrl · locale
Product
· sku · name · priceEur · stock
Order
· orderNo · total · status · createdAt
C Claude added relation User → Order
— / MCP server

Ten tools.Coming soon.

mockomat-mcp speaks the Model Context Protocol over STDIO. The npm package is coming soon — once it's out, add it once to Claude Desktop, Claude Code, or Cursor and your AI gains a new toolbox. Until then, any LLM can build mock APIs through the capability spec.

npm
# mockomat-mcp — npm package coming soon
Read the capability spec
MCP Tools
create_project Spin up a new mock project with slug and metadata
get_project_status Retrieve project state, tables, and endpoints
list_data_sources Browse the public data-pool catalog
get_data_source Inspect schema + sample rows of a source
create_table Add an entity with typed attributes
create_attribute Append a field to an existing table
create_relation Link two tables with cardinality
generate_api Publish the GraphQL endpoint for the project
query_data Run a GraphQL query against the live mock
import_openapi Parse an OpenAPI/Swagger spec into tables

What an LLM can and can't do, per tier.

The free entry points are wide enough for any prompt to succeed. Production workloads — CI integration, public demos, AI agents in the loop — live on a paid plan with API-key auth and higher quotas.

Guest

  • 1 project · session-based
  • 24h expiry
  • 100 API requests / day
  • Share-link endpoint, rate-limited per IP

Starter

  • 1 project
  • Persistent projects
  • 1,000 API requests / day
  • No external API (share links only)
  • 2 guest collaborators per project

Professional

  • 10 projects
  • Private endpoints & API keys
  • 10 API keys per project
  • 50,000 API requests / month
  • 11 team members

Business

  • 20 projects
  • 250,000 API requests / month
  • 50 API keys per project
  • 19 team members · 3 maintainers
  • Endpoint analytics