Schema First

A personal remote MCP server with four tools. The MCP endpoint is /mcp. It supports revision 2026-07-28 and the preceding revision 2025-11-25. All tool results include structured content matching their declared JSON Schema.

Tools

Failed tool calls return {error: "message"} as structured content with isError: true. Input and output schemas describe these cases. Rate limits apply; only one transcription runs at a time.

Sign-in and consent

Tool calls require an OAuth bearer token issued by this server, for this server’s resource only. Protected resource and authorization server metadata are public under /.well-known/. Clients can use HTTPS client metadata documents or dynamic registration. Registration does not grant access.

Authorization uses a browser, the owner’s password, explicit Approve/Deny consent, an exact registered redirect (with the loopback-port exception), and S256 PKCE. The owner must verify the displayed client and return address before approving. The tools scope grants access to all four tools and the shared notebook.

Codes expire after two minutes and are single-use. Access tokens last one hour. Refresh tokens last 14 days and rotate on use. The owner can revoke all access locally with manage.py revoke-all. There is no anonymous tool access and no third-party sign-in provider.

Data kept

This is one owner’s workspace, not a multi-tenant service. All clients the owner authorizes share all notes, including course verification notes. Do not grant access to clients that should not see them.

The owner can list/delete individual notes and uploads with manage.py, and clear transcript caches or audit logs locally. Deleting an upload disables its link, but cannot recall copies already downloaded. Nothing is sold or published apart from explicitly uploaded files, this plan, service health and OAuth metadata. Backups, if the owner makes them, need separate deletion.