real-fake-data-mcp
This server lets AI assistants discover and generate realistic, synthetic test data via two MCP tools:
list_generators: Retrieve all available generators with their IDs, descriptions, and supported locales (e.g.,pl.pesel,any.email,de.company-name). Use this first to explore what data types are available.generate: Run any generator by ID to produce fake-but-realistic data, including:Polish identifiers with valid checksums: PESELs, NIPs, REGONs
IBANs across 27 EU countries
Addresses drawn from real cities and streets
People (names, surnames, birth dates) with optional sex filtering
Company names, emails, and other generic data
Key features:
Batch generation: Use the
countparameter to produce multiple records in one call.Reproducible output: Pass a
seedvalue for deterministic, repeatable results — useful for consistent test fixtures.Generator-specific options: Customize via
options(e.g.,{ "sex": "f" }for female persons,{ "format": "digits-only" }for NIPs,{ "invalid": true }for deliberately wrong checksums to test validators).Auto-updating: New upstream generators become available immediately without client upgrades.
Configuration: Set
REAL_FAKE_DATA_API_KEYfor metered plans, orREAL_FAKE_DATA_API_BASE_URLto point to a custom API instance.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@real-fake-data-mcp Generate 5 Polish addresses for my test database"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@przeslijmi/real-fake-data-mcp
A Model Context Protocol server for Real Fake Data — gives an AI assistant (Claude Desktop, Claude Code, Cursor, …) realistic, synthetic test data on demand: valid PESELs (correct checksums), NIPs, REGONs, IBANs, addresses drawn from real cities and streets, people, and company names across 27 EU countries.
Output looks real but is fake — safe for staging, demos, and seed data.
Two tools, self-updating.
list_generatorsfor discovery,generateto run any generator by id. New generators on the API appear automatically — no client upgrade.Thin and stateless. Calls the hosted Real Fake Data API over HTTPS; no data is generated or stored locally.
Seeded when you want it. Pass a
seedfor reproducible output, or omit it to randomise each call.
Install
No global install needed — point your MCP client at the package via npx. It runs over stdio, so the client spawns it as a subprocess.
Claude Desktop / Claude Code
Add it to your MCP servers config (claude_desktop_config.json, or via claude mcp add):
{
"mcpServers": {
"real-fake-data": {
"command": "npx",
"args": ["-y", "@przeslijmi/real-fake-data-mcp"],
"env": {
"REAL_FAKE_DATA_API_KEY": "your-api-key"
}
}
}
}Restart the client; the real-fake-data tools become available in any conversation.
Requires Node 22+.
Related MCP server: Polish Business Intelligence MCP
Configuration
The client passes configuration through the server's env:
Variable | Required | Description |
| No | API key sent as |
| No | Override the hosted API. Defaults to |
Tools
list_generators
Lists every available generator with its id, description, and supportedLocales. Call it first to discover which ids generate accepts.
You: What fake-data generators are available?
Claude (calls
list_generators) →pl.pesel,pl.company,pl.address,any.email,de.company-name, …
generate
Runs one generator and returns the API's { data, meta } envelope.
Argument | Type | Description |
|
| Generator id from |
|
| Generator-specific query parameters; omit for defaults. |
|
| Number of records to generate; omit for a single record. (Upper bound enforced by your plan.) |
|
| Seed for reproducible output; omit to randomise each call. |
You: Generate 3 female Polish people for my staging DB.
Claude (calls
generatewith{ generator: "pl.person", count: 3, options: { sex: "f" } }) → three records of{ name, surname, initials, birthDate, pesel }.
options are the same query parameters the generator exposes on the REST API — list_generators describes each, and the API docs list them in full. Examples: { "format": "digits-only" } for a NIP, { "teryt": "14" } to anchor an address to a region, { "invalid": true } to get a deliberately-wrong checksum for testing your validators.
How it relates to the REST API
This server is a thin MCP front end over the same hosted endpoints the Playwright addon and REST API serve. A generator id maps directly to a route — pl.pesel → GET /v1/pl/pesel, any.email → GET /v1/email — and metering, plan limits, and validation all behave identically. Use this package when you want an AI assistant to produce test data conversationally; use the Playwright addon or the REST API directly from code.
License
MIT
This repository is auto-generated from a private upstream monorepo. Open issues here, but code changes are made upstream and re-synced — pull requests against this repo are applied upstream, not merged directly.
Available Tools
2 toolsgenerateGenerate realistic fake dataA
Generate realistic synthetic data from one Real Fake Data generator. Pass a generator id from list_generators (e.g. pl.pesel). Use options for generator-specific parameters (e.g. {"sex":"f"} for a person, {"format":"digits-only"} for a NIP) — see each generator's description. Set count for a batch and seed for reproducible output. Returns the API's { data, meta } envelope.
Inputs: generator (required), options, count, seed.
list_generatorsList Real Fake Data generatorsA
List every available Real Fake Data generator with its id, description and supported locales. Call this first to discover which generator ids the generate tool accepts (e.g. pl.pesel, pl.company, any.email).
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one lists available generators, the other generates data. There is no overlap or ambiguity.
Both tools use imperative verbs, but 'list_generators' follows a verb_noun pattern while 'generate' is just a verb, creating a slight inconsistency. The pattern is still clear and readable.
Two tools is minimal but appropriate for the server's purpose of discovering and generating synthetic data. The scope is well-defined without unnecessary extras.
The tools cover the essential workflow: discover generators and generate data. There is a minor gap in not having a tool to view detailed generator options, but the descriptions in list_generators suffice for basic use.
Maintenance
Related MCP Connectors
Generate realistic, FK-consistent synthetic test data for your databases from your AI assistant.
Format-true synthetic test data for 90 countries — IBANs, SWIFT/BIC, IDs, cards, all certified.
Generate synthetic random user data for testing, demos, and development without using real persona.
Privacy-safe synthetic financial data for LatAm fintech, AI agents, testing and ML.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceGenerates realistic, context-aware synthetic data for AI agents to populate databases, mock APIs, and create test scenarios without exposing real PII.7 npm3-
- AlicenseAqualityDmaintenanceProvides AI agents with real-time access to Polish official data: VAT whitelist for company verification and NBP exchange rates, enabling checks on VAT status, company details, and currency conversion without API keys.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to verify Polish companies and EU VAT numbers against official government registries using 9 tools, with no API key and optional plain REST access.MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI assistants access to Polish public registers, enabling company lookups in KRS, VAT whitelist and bank-account checks, KRS extract retrieval, and offline validation of NIP, REGON, KRS, NRB, and KW numbers.MIT