Use Scalpels from your agent

The Scalpels MCP server installs once at the user level of any agent harness. That one connection gives your agent the public catalog and documentation, and a token adds your teams and their MCP-enabled products.

Install

Create a token on the Agent access page, /settings/agent-access, under Profile settings. That page shows two installation formats once, when the token is created.

The first is the hitch command, using the claim code shown on that page. It runs through npx, so hitch does not need to be installed first:

npx hitch-mcp install https://scalpels.app/mcp --claim YOUR-CLAIM-CODE --claim-url https://scalpels.app/mcp/claim

The second adds the server and the revealed token to your harness's JSON MCP configuration:

{
  "mcpServers": {
    "scalpels": {
      "url": "https://scalpels.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR-TOKEN"
      }
    }
  }
}

Scalpels supports HTTP transport only. The public catalog and documentation work without a token.

Learn the fleet

Talk to me about how the tools in Scalpels might fit into our development workflow.

Without an account, your agent can read the catalog, product pages, documentation, and integration guides. The product information includes each application's capabilities, infrastructure requirements, environment keys, and available guides.

Wire a site up

Get telemetry set up on my Forge-deployed sites.

With a token, your agent can find the Forge sites and Cloud environments that an installed provider is not hearing from, explain anything that must be fixed first, and ask you to confirm each connection. Scalpels returns a branch and, where the repository's plan allows, a draft PR. Your agent then checks out the branch, updates the affected Composer packages, and pushes it; you merge and deploy, and the agent refreshes and checks the connection until the provider reports it.

Ask the fleet

Tell me which of my projects have thrown exceptions in the last hour.

With the Call installed apps ability, your agent can list the MCP-enabled products the team runs, inspect their available tools, and relay a call to the selected deployment. The product applies your role to the call.

Talk back

Report this to Scalpels.

Your agent can file a bug report with relevant deployment context, reply to the resulting support thread, or search existing suggestions before proposing a product or tool that does not exist yet.

Abilities

Abilities are granted when a token is created on the Agent access page.

Read (always on)

Lets your agent see your teams, sites, connection status, the catalog and docs. It also files bug reports and suggestions on your behalf, and replies to them.

Connect sites

Lets your agent connect a Forge site or Cloud environment to a product you run. Each connection writes the product's keys into that site's environment file. Your agent is told to confirm each site with you first.

Call installed apps

Lets your agent call the tools of the MCP-enabled products installed on your teams, as you, with your role in each. Only deployments whose recorded metadata offers delegated MCP access are reachable this way.

What passes through Scalpels

When an agent relays a call to an installed product, the call and its answer pass through Scalpels. Scalpels does not intentionally persist that content in any store it controls (database, cache, session, queues, files, logs, traces, analytics, error reports); records only who asked which product for what, when, and whether it succeeded

That content transits Scalpels' memory and is not end-to-end encrypted.

Everything is deployed on the customer's own Laravel Cloud or Forge, and Scalpels holds no product data.

Per-installation sign-in

Whether an app uses Scalpels for sign-in is chosen per installation by that app's Owner, inside the app. There is no team-wide switch.