mega-mcp

A personal remote MCP server. Its endpoint is /mcp. Only clients the owner lets in can use it.

What the tools do

Every tool result is structured content that matches the tool's declared output schema.

How sign-in works

The server uses OAuth 2.1 with PKCE (S256). Clients register by Client ID Metadata Document or Dynamic Client Registration, then send the owner to /authorize. The owner reads the client's name and redirect address, enters the owner password, and approves or denies.

Access tokens last one hour and work only on this server's /mcp endpoint. Refresh tokens last 30 days and can be used once each. Rotating the server's signing secret ends every grant.

What data it keeps