Skip to main content
Glama

MCP Browser Agent

by ashley-ha

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Schema

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Tools

Functions exposed to the LLM to take actions

NameDescription
get_planner_state

Get the current browser state and planning context. This tool must be executed before execute_actions tool.

Must return a JSON string in the format: { "current_state": { "evaluation_previous_goal": "Success|Failed|Unknown - Analysis of previous actions", "memory": "Description of what has been done and what to remember", "next_goal": "What needs to be done with the next immediate action" }, "action": [ {"action_name": {"param1": "value1", ...}}, ... ] }
execute_actions

Execute actions from the planner state.

Args: actions: A dictionary containing the planner state and actions in format: { "current_state": { "evaluation_previous_goal": str, "memory": str, "next_goal": str }, "action": [ {"action_name": {"param1": "value1"}}, ... ] } Note: If the page state changes (new elements appear) during action execution, the sequence will be interrupted and you'll need to get a new planner state.

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/ashley-ha/mcp-manus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server