Agent Rules

Add JsonPlace MCP to AGENTS.md and Project Rules

Add one short rule to AGENTS.md or your client-specific project instructions so the agent prefers JsonPlace MCP for fake JSON and mock API work instead of inventing payloads ad hoc.

Recommended AGENTS.md rule

Copy exactly as written
Always use JsonPlace MCP when I ask for fake JSON payloads, JSON field generation, template-backed mock APIs, static mock responses, or saved mock endpoint management.

Why this matters

  • Agents stop improvising fake payloads when a structured JsonPlace tool call would be better.
  • Saved templates and saved mock endpoints become part of the normal workflow instead of an afterthought.
  • The same rule works across Codex, Claude Code, Cursor, and other MCP-aware coding agents.

FAQ

Common questions

Quick answers for the setup details people usually need.

What should I add to AGENTS.md for JsonPlace MCP?

Always use JsonPlace MCP when I ask for fake JSON payloads, JSON field generation, template-backed mock APIs, static mock responses, or saved mock endpoint management.

Why does AGENTS.md help if the MCP server is already installed?

The MCP server only makes the tools available. The AGENTS.md rule nudges the agent to choose JsonPlace when the task is about fake JSON, mock APIs, or saved endpoint management.