Faker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate-personC | Generates fake person data including names, emails, phone numbers, and addresses |
| generate-companyB | Generates fake company data including names, industries, contact information, and addresses |
| generate-datasetB | Generate a structured dataset with multiple related entities and referential integrity. Supports person, company, and custom entity types with one-to-many and many-to-many relationships. Perfect for creating test databases, mock APIs, and complex data scenarios. |
| generate-customC | Generates fake data following custom patterns, including regex patterns, enums, formats, and ranges |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools have overlapping purposes that could cause confusion, particularly between generate-company and generate-person which both produce contact/address data, and generate-custom which can likely replicate functionality of the others. However, generate-dataset stands out clearly for complex scenarios, and descriptions help differentiate them to some extent.
All tool names follow a perfectly consistent verb-noun pattern with kebab-case (generate-company, generate-custom, generate-dataset, generate-person). This predictable naming makes the set easy to navigate and understand at a glance.
Four tools is a reasonable number for a fake data generation server, covering core entity types and advanced scenarios. It feels slightly thin as it lacks tools for other common fake data types like products or financial data, but the scope is well-defined and manageable.
The server covers basic fake data generation for persons and companies, plus custom patterns and datasets, but has notable gaps. Missing are tools for other common fake data categories like addresses alone, products, or financial records, and there's no update/delete functionality for generated data, limiting lifecycle coverage.