chromium-arm64
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROMIUM_WINDOW_SIZE | No | Set browser window size | 1280,720 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| navigateC | Navigate to a URL |
| screenshotB | Take a screenshot of the current page |
| clickC | Click an element on the page |
| fillC | Fill an input field |
| evaluateC | Execute JavaScript in the browser |
| get_contentC | Get page content (HTML or text) |
| hoverC | Hover over an element on the page |
| selectC | Select an option from a dropdown |
| get_console_logsB | Get browser console logs |
| get_console_errorsB | Get browser console errors |
| get_network_logsC | Get network activity logs |
| get_network_errorsC | Get network error logs |
| wipe_logsB | Clear all stored logs from memory |
| get_selected_elementB | Get information about the currently selected element |
| run_accessibility_auditB | Run an accessibility audit on the current page |
| run_performance_auditC | Run a performance audit on the current page |
| run_seo_auditB | Run an SEO audit on the current page |
| run_best_practices_auditC | Run a best practices audit on the current page |
| run_nextjs_auditB | Run a Next.js specific audit on the current page |
| run_debugger_modeC | Run debugger mode to debug issues in the application |
| run_audit_modeC | Run comprehensive audit mode for optimization |
| close_browserB | Close the browser instance |
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/nfodor/mcp-chromium-arm64'
If you have feedback or need assistance with the MCP directory API, please join our Discord server