M
mcp.read
Read AI captures and organizes meeting data such as transcripts, summaries, action items, and related analytics. It provides users access to that meeting data through its web app and programmatic interfaces.
mcp.read maps to Read AI’s developer surfaces on `api.read.ai`: one REST API and one remote MCP server, both authenticated with Read-issued OAuth 2.1 user-authorized bearer tokens obtained via dynamic client registration.
discovered 2mo ago
MCP servers1
- Read AI MCP serverdetected
REST · OpenAPI1
- Read AI REST APIdiscovered
Credentials
OAuth 2.0oauth2
OAuth 2.0 — self-onboarding
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing