MCP is finally here: stop building REST boilerplate and start shipping BugiaData has launched a hosted remote MCP server (SSE) that lets AI agents generate relational fake data with valid foreign keys directly from editors like Cursor, Claude, and Windsurf. The service provides four tools—ping, whoami, generate_data, and generate_relational_data—with a free tier of 10,000 tokens per month, eliminating the need for custom REST boilerplate. TL;DR:BugiaData MCP is live. Point Cursor, Claude, or Windsurf at a hosted SSE server, paste one config block, and ask your agent for relational fake data with valid foreign keys—no custom REST glue in your repo. If you build with AI agents, you already know the loop: The Model Context Protocol was supposed to fix the integration tax. In practice, a lot of “MCP-ready” products still feel like REST APIs wearing a badge—same docs maze, same “here’s your API key, good luck.” I built BugiaData https://bugiadata.com to skip that layer for one job: generating fake data that actually behaves like a database —locales, multiple tables, foreign keys intact—directly from the chat in your editor. BugiaData now exposes a hosted remote MCP server SSE with four tools: | Tool | What it does | |---|---| ping | Health check + tier hint | whoami | Quota and account info for your API key | generate data | Single Faker-type batch names, emails, etc. | generate relational data | Multi-table JSON with foreign key columns wired correctly | Same API key and monthly quota as the REST API and Studio. Free tier: 10,000 tokens/month . Works today in Cursor , Claude Desktop , Claude Code , and Windsurf . REST is fine for humans. For agents, every endpoint is another chance to hallucinate paths, forget headers, or invent query params. With MCP: BugiaData’s differentiator isn’t “fake data exists.” It’s relational consistency : users and orders where orders.user id actually references users.id , in pl PL or pt BR if you ask for it. Flat Faker lists are easy. Graph-shaped test data is where projects stall. That’s the wedge. Sign up free : bugiadata.com/signup https://bugiadata.com/signup Open Dashboard → MCP and copy your key: bugiadata.com/dashboard?tab=mcp https://bugiadata.com/dashboard?tab=mcp Cursor — .cursor/mcp.json project or global : { "mcpServers": { "bugiadata": { "url": "https://mcp.bugiadata.com/sse", "headers": { "X-API-Key": "YOUR API KEY" } } } } Claude Desktop / Claude Code / Windsurf — same mcpServers block in your client config claude desktop config.json , ~/.claude/mcp.json , or Windsurf MCP config . Restart the client after saving. Try something concrete: Using BugiaData, generate 20 users and their orders. Orders must reference users.id. Use locale pt BR. Or a single-type batch: Generate 10 company names and emails with locale en US via BugiaData. The agent should call generate relational data or generate data and return JSON in chat—no shell scripts, no hand-rolled fetch. The MCP landing page includes a live demo rate-limited ping / sample generation so you can watch JSON come back before creating an account: Full docs REST + schema shape : bugiadata.com/docs https://bugiadata.com/docs io.github.lgpoliveira/bugiadata-mcp — If you’re already on MCP in production: Drop a comment or open an issue on the docs repo. I’m especially interested in real agent prompts that broke—or surprised you—in a good way. Links