Skip to content
PageSugar Open setup instructions

Free MCP access. Public and read-only.

Give your agent the source.

Connect your coding agent to PageSugar to search and retrieve website sections for Svelte 5 and Tailwind CSS 4. The catalogue supplies the source; your agent integrates it.

Connect your agent Open setup instructions
Setup guides for
The connection
  • Streamable HTTP
  • No sign-in
  • No API key

01 / Connect

Pick your agent. Follow its setup.

One server URL, with setup steps for each client. Choose a method below, then check that your agent can make a catalogue request.

Server URL https://pagesugar.com/mcp

Use this URL in the server settings, command or config shown for your selected client.

Showing setup for VS Code.

VS Code

GitHub Copilot

Install in VS Code

Choose one setup method. Complete any client trust prompts before using the tools.

  1. Option A Terminal

    Adds the server to your user profile.

    Terminal 
    code --add-mcp '{"name":"pagesugar","type":"http","url":"https://pagesugar.com/mcp"}'

  2. Option B Config file

    Note the top-level key is servers. For your user profile, run MCP: Open User Configuration instead.

    .vscode/mcp.json 
    {
  "servers": {
    "pagesugar": {
      "type": "http",
      "url": "https://pagesugar.com/mcp"
    }
  }
}

Check the connection. Run MCP: List Servers from the Command Palette, then use Copilot Chat in agent mode.

Then ask your agent to call PageSugar’s list_categories. A returned result confirms access; saving configuration alone does not.

Follows the VS Code documentation, checked 17 September 2026. This is documentation evidence, not an end-to-end PageSugar test.

The server returns catalogue information and source. Your agent applies any change to your project, under your client’s permissions. What it can and cannot do

Help with setup

Let your agent help you connect.

Copy the setup instructions and ask your agent to help configure the connection. You may still need to approve access, change a setting or start a new session.

Open setup instructions View the Markdown

02 / Ask

Then just ask for what you need.

Name PageSugar in your request. Start by inspecting a component, or ask your agent to add one.

  • Add a section

    Find a pricing section with three plans in PageSugar and add it to my landing page. Match my existing colours.

  • Choose with constraints

    Search PageSugar for a newsletter signup with no extra runtime packages. Explain the email service I need to provide. Show me what you find before you add anything.

  • Check before you commit

    Look up the FAQ accordion in PageSugar. Tell me what it depends on and which files it would add. Do not change my project yet.

  • Browse

    List the PageSugar categories and tell me what is available for a marketing site.

Illustrative workflow · after connection

You

Use PageSugar to add a pricing section with three plans.

Your agent
  1. search_components Finds the closest matches
  2. get_component Checks dependencies and limits
  3. get_component_files Returns source and a file manifest
  4. Your agent · integrate Adds the complete files and adapts the content
  5. Your agent · check Runs project checks and reviews the page in a browser

Pricing section integrated and checked.

03 / Boundaries

It answers questions. Your agent does the work.

The server returns catalogue information and source. Anything that touches your project is done by your agent, under your client’s permissions.

What it can do

  • Search the catalogue from a plain description of what you need.
  • List categories and browse every published component with filters.
  • Read a component's versions, variants, props, usage, dependencies and license.
  • Return a file manifest and source for an exact version; large responses need separate file retrieval.
  • Give the ZIP bundle location with its SHA-256 checksum.

What it cannot do

  • It cannot write to your project. Your agent applies changes under your client’s permissions.
  • It cannot run code, installers or shell commands.
  • It cannot read your files, your environment or anything outside the catalogue.
  • It contains no language model. Your agent does the reasoning.

Send only what the tools need: a description of the component and public constraints such as “Svelte 5, no extra dependencies”. Never your source code, credentials or personal data. Treat a search query as something sent to a public service.

04 / Tools

7 tools. All of them read-only.

Nothing here can change the catalogue or your project. The tools return catalogue information, source and download locations.

01 /

Discover

Find what the catalogue has.

  • list_categoriesLearn the categories and what each one holds.
  • list_componentsBrowse every published component with filters and pagination.
  • search_componentsFind the best matches for a described need.
02 /

Inspect

Decide whether it fits.

  • get_componentInspect versions, variants, props, usage, dependencies and limits.
03 /

Retrieve

Bring the exact source home.

  • get_component_filesGet the file manifest and runtime text when it fits. Retrieve binary assets separately.
  • get_component_fileRead one file, or a line range of it.
  • download_componentGet the ZIP bundle location, its checksum and the receipt.

05 / Help

If something is not working.

The server is configured, but the tools are missing.

A saved entry is only the first step. Check the selected client’s connection status and any pending trust or approval prompt. Follow its instructions if a session reload is needed, then request list_categories from PageSugar.

My agent is not using PageSugar.

Name PageSugar in your request and ask it to call list_categories. A returned catalogue result confirms tool access; a description of available tools alone does not.

The source was retrieved, but my page has not changed.

Retrieval returns source. Ask your coding agent to integrate the complete file set into your project, follow the usage notes and run the project checks.

The requested version is unavailable.

The service retains current releases only. Inspect the available version and decide whether to use it. Never silently substitute it for the requested release; keep downloaded files and their receipt for future use.

The client cannot connect.

Check that your client supports remote servers over Streamable HTTP and that the URL is exact, including the /mcp path. Clients that only speak stdio or the older SSE transport cannot connect directly.

Opening the endpoint in a browser shows this page.

That is expected. Browsers get this page; MCP clients send POST requests to the same URL and get the protocol.

My client only supports local (stdio) servers.

Use the mcp-remote bridge. Set the command to npx and the arguments to -y, mcp-remote and the endpoint URL.

A browser-based client is rejected with 403.

Requests that carry an Origin header are only accepted from allowed origins. Requests without an Origin header are not subject to that origin check.

Files are missing from a result.

Check contentStatus. "manifest-only" means the release is larger than one response, so your agent should fetch files with get_component_file or use the bundle. Binary assets are never inline text: retrieve their sourceUrl and verify sha256, even when contentStatus is complete.

One URL. The whole catalogue.

Give your agent a starting point you can preview, inspect and adapt.

Connect your agent Browse components