mcp-page-capture
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| captureScreenshotA | Capture webpage screenshot with optional pre-capture interactions. PARAMS: • url (required): Page URL • steps (optional): Array of 6 step types (order auto-fixed) • headers (optional): HTTP auth headers • validate (optional): Dry-run step validation 6 STEPS (all optional, order doesn't matter): • viewport: { device: "mobile" } - Set device/screen • wait: { for: ".loaded" } or { duration: 2000 } - Wait for element or time • fill: { target: "#email", value: "a@b.com" } - Fill form field • click: { target: "#btn", waitFor: ".result" } - Click element • scroll: { to: "#footer" } or { y: 500 } - Scroll page • screenshot: { fullPage: true } - Capture (auto-added if omitted) COMMON ERRORS & FIXES: • ELEMENT_NOT_FOUND → Add wait step before the failing step • ELEMENT_NOT_VISIBLE → Add scroll step before the failing step EXAMPLE: { "url": "...", "steps": [{ "type": "fill", "target": "#email", "value": "a@b.com" }, { "type": "click", "target": "#submit", "waitFor": ".dashboard" }] } |
| extractDomA | Extract HTML, text, and DOM structure from a webpage. USE WHEN: Need text content for analysis, DOM structure for selector discovery, or pre-capture page validation. USE captureScreenshot WHEN: Need visual verification or rendered UI. • url (required): Page URL • selector (optional): CSS selector to scope extraction (e.g., 'main', 'article') EXAMPLE: { "url": "https://example.com", "selector": "article" } |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/chasesaurabh/mcp-page-capture'
If you have feedback or need assistance with the MCP directory API, please join our Discord server