Enrichr Web Capture

dev.enrichrPublished by enrichr.devOfficial publisherv1.0.0Updated Oct 24, 2026

See the rendered web: design tokens, fonts, animation timings, WebGL shaders and 3D from any URL.

VerifiedStreamable HTTPWeb executableBrowser AutomationMedia & Design

Overview

AI-generated overview

A remote MCP server that lets an assistant capture and inspect the rendered web from any URL, including design tokens, fonts, animation timings, WebGL shaders,

What you can do
Capture and inspect the rendered appearance of a web page from a URL, including design tokens, fonts and animation timings. Extract WebGL shaders and 3D content from a page. The manifest lists no individual tools, so exact operations are not documented; capabilities are inferred from the description.
When to use it
Useful when an assistant needs to see how a page actually renders rather than its raw markup, for example to study a site's design system, typography, motion or 3D and WebGL work.
Requirements
A remote streamable HTTP endpoint at enrichr.dev, reachable over the network. Authentication is required: OAuth, plus an Enrichr API key sent in the X-API-Key header. The key starts with enrichr_ and is available free from the provider's account page.
Before you install
An API key is required and must be supplied in the X-API-Key header; treat it as a secret. Captured URLs and page content are sent to the third-party service, so avoid pages with sensitive or private data.

Installation

In SourceWeft

  1. Open Enrichr Web Capture 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.enrichr%2Fweb-capture/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": {
    "enrichr-web-capture": {
      "type": "http",
      "url": "https://enrichr.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

1
  1. v1.0.0LatestOct 14, 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.

Other Enrichr integrations