Recipe

How to create a saved static JSON mock endpoint with JsonPlace MCP

Ask your agent to create a static JsonPlace endpoint, provide the endpoint path, and provide the exact JSON body you want returned. JsonPlace MCP will save the endpoint and give you a public mock URL.

Prompt to use with your agent

Prompt
Create a static JsonPlace endpoint at config/flags that returns {"beta":true,"region":"eu","maintenance":false}.

Example static response

JSON
{
  "beta": true,
  "region": "eu",
  "maintenance": false
}

How it works

  1. Add the hosted JsonPlace MCP server

    Point your MCP client at https://jsonplace.com/mcp. Public mode works without any Authorization header.

  2. Describe the endpoint path and exact response

    Static endpoints are best when you want a fixed response body instead of generated values.

  3. Share the public URL with your app or test

    Once the endpoint is saved, your agent can return the public URL so you can plug it directly into clients or test fixtures.

Next steps

  • Keep the public mock URL for integration tests, demos, or agent workflows.
  • Save the prompt in your project docs if the workflow is something you repeat often.
  • Add the AGENTS.md rule from the instructions page so the agent prefers JsonPlace MCP automatically.

FAQ

Common questions

Each recipe page answers the exact workflow it demonstrates.

When should I use a static JsonPlace endpoint instead of a template-backed one?

Use a static endpoint when every request should return the same JSON. Use a template-backed endpoint when you want new fake values on each request.