OpenX MCP Server resources
This page answers which resources the OpenX MCP server lists and when an AI should read each one. A resource is a document the client reads by id, as opposed to a tool it calls.
The two static resources
| Resource | What it holds |
|---|---|
proposal_schema | The full proposal group structure manage_proposals takes. Read it before building a proposal. |
api_spec | The OpenAPI 3.1 spec of the OpenX api, filtered to the routes your access allows. |
proposal_schema also carries the edges between kinds and the guide for proposing a job identity. If the api
spec cannot be read, api_spec holds only an error that says so; ask again shortly.
Per-kind resources
For each node kind that is on in the workspace, the session adds a schema/<kind> resource (the kind's
JSON Schema, with field descriptions) and the kind's example resources. An example holds its description, the
proposed record, a ready manage_proposals call and notes. get_workspace names each kind's resource ids
under Capabilities.Kinds, and with includeGuides: true returns the schema and examples themselves.
Resource templates
The server lists no resource templates today.