Screenshot
com.apiscreenshotPublished by apiscreenshot.comOfficial publisherv1.1.0Updated Oct 24, 2026
Screenshot any URL/HTML as PNG/JPEG/WebP, or read it as clean Markdown/text for LLMs.
Overview
Lets an assistant capture any URL or HTML as a PNG, JPEG or WebP image, or read it back as clean Markdown or plain text.
- What you can do
- This remote MCP server renders a given URL or raw HTML and returns the result either as a screenshot image in PNG, JPEG or WebP format, or as extracted clean Markdown or plain text suited to language models. It is a hosted service reached over streamable HTTP, so no local package is installed. The registry description lists no individual tool names.
- When to use it
- Useful when an assistant needs a visual snapshot of a web page, or needs page content converted into readable Markdown or text without running a browser locally. Suited to workflows that combine page capture with text extraction.
- Requirements
- A remote MCP endpoint at apiscreenshot.com over streamable HTTP. Authentication is required: a bearer API key sent in the Authorization header, in the form Bearer sk_live_... . A free account can be created with the provider. Network access to the provider is needed.
Installation
In SourceWeft
- Open Screenshot in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- 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/com.apiscreenshot%2Fscreenshot/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"screenshot": {
"type": "http",
"url": "https://apiscreenshot.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
28% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- 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.