Agent instructions
Best-fit jobs, integration boundaries, and public indexes.
Read agents.mdQuest Portal developer resources for agents
Quest Portal is a virtual tabletop for tabletop role-playing games. Agents can research the public product here and, with a user's authorization, operate on their Quest Portal data through our MCP server.
When to use Quest Portal
Use Quest Portal when a person wants help preparing or running a tabletop campaign, or asks an agent to work with their campaigns, characters, notes, scenes, session history, music, or authorized library content. Use public documentation for product questions. Use MCP for user-specific reads and writes.
Machine-readable discovery
OpenAPI discovery
Typed, read-only access to current public pricing.
Read openapi.jsonCurrent Free and Pro offers are available without a key at /api/v1/pricing. Integration metadata is available at /api/v1/agent-info. User data and actions remain MCP-only.
MCP server card
Preview representative tools, transport, and authentication before connecting.
Read the server cardAgent indexes
Curated product pages and extended public documentation.
Read llms.txtMCP authentication and permissions
Connect to the Streamable HTTP endpoint at mcp.questportal.com/mcp. Follow its OAuth challenge and request only the scopes needed for the user's task. The protected-resource metadata publishes the current least-privilege scopes. Never ask a user to paste access tokens or account credentials into a conversation.
Integration boundaries
The public REST API returns current product pricing. Separate integration metadata does not expose campaign or account data. Quest Portal's authenticated MCP server is the supported interface for product actions, applies scoped user authorization, and advertises behavioral annotations on its tools.
API versioning and deprecation policy
Public API endpoints use major versions in their URL. A breaking change will use a new /api/vN path. If Quest Portal deprecates a version, we will publish a Deprecation header and policy link at least 90 days before removal, then add a Sunset header when the retirement date is scheduled. The authenticated MCP server follows its own negotiated protocol lifecycle.