Spache

Use Spache with an AI agent

Connect Spache’s remote MCP server to an MCP-compatible coding agent. Once connected, you can ask the agent to inspect your sites, review route activity, and make approved changes using ordinary instructions.

Connect the Spache MCP server

  1. In your AI client, add a remote MCP server.
  2. Use this server URL: https://spache.online/mcp
  3. Connect. Spache will open a sign-in and authorization page in your browser.
  4. Sign in to Spache and approve the requested access. Review the permissions before accepting.

The exact setup controls vary by AI client. Choose its remote MCP server option rather than configuring a local command or installing a package.

What you can ask it to do

  • “List my Spache sites and show me their preview URLs.”
  • “Show the last 7 days of traffic and render stats for my Mid Engine site.”
  • “List my most-requested routes and show any recent render failures for /products/widget.”
  • “Change this site’s cache lifetime to one hour.”
  • “Clear only the cache for /products/widget.”

Available capabilities

  • list_sites and get_site show your sites, preview URLs, and supported settings.
  • get_site_stats and list_routes report recent usage and route activity (up to 30 days).
  • get_route_failures inspects recent recorded failures for a route.
  • connect_site creates a Spache configuration for an already-deployed public SPA; it does not deploy your application or connect a custom domain.
  • update_site_settings can change the origin, cache lifetime, render waits, ignored routes, and request capture rules.
  • clear_site_cache and clear_route_cache invalidate cached content.
  • create_cache_webhook creates a deployment/content invalidation URL.

Permissions and safety

Reading site information requires read access. Connecting sites, changing settings, clearing caches, and creating webhooks require write access. The agent can only access sites in the Spache account you authorize.

Ask the agent to inspect settings before changing them, and be explicit about the site and route you mean. Cache clears make the next request fetch fresh content and can trigger a render. A cache webhook URL is secret; creating a replacement invalidates the previous URL, so only ask for one when you intend to create or rotate it.

You can review or disconnect connected agents under Account → Developer access.