Frontshelf

io.frontshelfPublished by frontshelf.ioOfficial publisherv0.4.0Updated Oct 24, 2026

Fix the site issues Frontshelf finds, then have Frontshelf verify each fix.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant fix site issues that Frontshelf finds and then have Frontshelf verify each fix.

What you can do
Frontshelf is a remote MCP server reached over streamable HTTP. Its stated purpose is to let an assistant fix the site issues Frontshelf finds and then have Frontshelf verify each fix. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant to work through website issues surfaced by Frontshelf and confirm that each fix actually resolved the problem. It suits a fix-and-verify loop on a site already connected to Frontshelf. It is not described as useful for unrelated tasks.
Requirements
A remote streamable HTTP endpoint at Authentication is required: a bearer token in the Authorization header, described as a Frontshelf agent key, which the user creates in the Frontshelf app. No packages, environment variables, or other credentials are declared. Network access to the endpoint is needed.
Before you install
The server requires a bearer credential in the Authorization header, described as a Frontshelf agent key; treat it as a secret and avoid exposing it in logs or shared configuration. The description implies the assistant can act on site issues and then have fixes verified, so changes made to a site should be reviewed before being applied. No payment, wallet, or private-key behavior is described.

Installation

In SourceWeft

  1. Open Frontshelf in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.frontshelf%2Ffrontshelf/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "frontshelf": {
      "type": "http",
      "url": "https://frontshelf.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v0.4.0LatestOct 15, 2026
  2. v0.3.0Oct 11, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.