Bring your MAXAEO evidence into another workflow.
Use personal mxa_ keys for read-only access through the REST API and MCP server. Inspect supported sites, visibility, run, task, change and crawler data without giving the connection publishing powers.
Pro is in beta: join the waitlist and we’ll tell you when it opens. No payment is taken.
Two protocols, one read-only boundary.
Illustrative exampleChoose REST or MCP and inspect the request and example response.
Read-only access to supported account data.
Static sample with a placeholder key. No network call or client connection is made.
Choose a protocol for the same bounded job
REST endpoints expose supported resources. MCP exposes the supported tools to a compatible client. The connection is for reading account data; it does not grant arbitrary database access, task writes or website changes.
Review personal access and keys in account settings before configuring a read-only connection.
Validate the real client before relying on it
The MCP server has not yet been tried from a real external MCP client. Examples should show placeholders instead of live keys, list supported operations and make unavailable data explicit.
For questions inside the product, the data assistant provides a separate read-only route to available account evidence.
How it works
- Create a personal key through the enabled account settings.
- Configure a supported REST request or MCP client.
- Read the permitted data and keep the key private.
What to know before you use it
- Read-only operations only.
- Personal keys use the mxa_ prefix and must be kept private.
- No real external MCP client has been tested.
- Access depends on the account's enabled beta access.
Questions
Can an MCP client publish a fix?
No. The described server exposes read-only access.
Has a real external client been tested?
Not yet; that validation remains outstanding.
Choose how to continue.
Use the relevant tool, or ask MAXAEO for a specialist review of the evidence and priorities.