Schema | Assert

Assert

Describes the environment variables required to run the server.

Name	Required	Description	Default
`ASSERT_API_KEY`	Yes	Your Assert API key obtained from the Assert dashboard (dashboard.assert.click).

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
assert_listA	List existing E2E test scenarios saved in Assert. Use this to audit coverage before generating new tests. Supports filtering by project and pagination.
assert_generateA	Generate a ready-to-run E2E test scenario in Assert Markdown format from a plain-English description. Optionally save it to Assert for later execution.
assert_runA	Execute a test scenario and return a run ID. Accepts either a saved scenario_id or ad-hoc markdown. Runs are async — use assert_status to poll for completion.
assert_statusA	Poll a test run for its current status and step-level results. Returns pass/fail with actionable failure details and screenshot URLs for failed steps.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pixel-Funnel/assert-click-mcp'

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