MCP for Copilot DirectoryMethodologySubmit / Get featuredNewsletter

← Directory

Toreva Goals

Durable, user-controlled goals and governed plans for AI agents.

likely compatible

OAuth with discovery metadata and Dynamic Client Registration; use OAuth 2.0 → Dynamic discovery.

Rule R2c · what this means · Not tested in Copilot Studio.

Registry nameio.github.toreva/goals
Endpoint used for verdicthttps://gateway.toreva.com/mcp?surface=goals
Transportsstreamable-http
Auth (Copilot Studio setting)OAuth 2.0 – Dynamic discovery
Last endpoint check2026-10-20T18:17:22Z · HTTP 401
Websitehttps://toreva.com/connect-claude?utm_source=official_mcp_registry&utm_medium=directory&utm_campaign=first_real_goal&utm_content=toreva_goals
Version0.1.0
Registry updated2026-08-28
Track changes like this weekly. New Copilot-ready MCP servers, breakages and auth changes, in one short email.
Is this wrong or out of date? Email us. Data built 2026-10-20.