Shotlane

dev.shotlanePublished by shotlane.devOfficial publisherv1.0.1Updated Oct 25, 2026

Screenshot web pages, read them as clean Markdown (JS rendered), and render HTML to PDF.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBrowser Automation

Overview

AI-generated overview

Shotlane is a remote MCP server that lets an assistant screenshot web pages, read them as clean Markdown with JavaScript rendered, and turn HTML into PDF.

What you can do
Capture screenshots of web pages through a remote endpoint. Read pages as clean Markdown with JavaScript rendered. Render HTML content to PDF.
When to use it
Useful when an assistant needs a visual capture of a live page, a readable text version of a JavaScript-heavy page, or a PDF generated from HTML, without running a local browser.
Requirements
A remote MCP connection to the Shotlane endpoint over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth sign-in to a third-party service, so review what account data and page content are shared with it. Pages submitted for capture or rendering are sent to that service.

Installation

In SourceWeft

  1. Open Shotlane in the dashboard and add it to a workspace.
  2. Connect the required 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/dev.shotlane%2Fshotlane/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "shotlane": {
      "type": "http",
      "url": "https://shotlane.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 25, 2026
  2. v1.0.0Oct 18, 2026

Score

83% 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
  • Documentation15 pts
  • 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.