This is an HTTP MCP server that takes Google Drive URLs and converts them to Markdown.
This is not a standalone server and has to be placed behind Pomerium Proxy, that manages the OAuth2 flow with Google Drive, and additional user authentication enforcement.
This is not an official Pomerium product.
You should have an account with Google Cloud.
- Enable Google Drive API https://console.cloud.google.com/apis/api/drive.googleapis.com
- Create OAuth2 application https://console.cloud.google.com/auth/clients
- Set Redirect URL to
https://markdown.YOUR-DOMAIN.com/.pomerium/mcp/oauth/callback - Set Authorized Javascript Origins to
https://markdown.YOUR-DOMAIN.com
Install with Kustomize:
kubectl apply -k github.com/pomerium/mcp-markdown/k8scheck your deployment:
kubectl rollout status deployment/mcp-markdown -n pomerium-mcp-markdownInstall and configure Pomerium Ingress controller that would front your HTTP MCP Servers.
Pomerium uses a dedicated pomerium IngressClass and does not interfere with your existing controllers.
Create Ingress and OAuth2 Secret using examples provided and deploy them to your cluster in the pomerium-mcp-markdown namespace.
routes:
- from: https://markdown.mcp.your-domain.com
to: http://localhost:8000
name: Markdown
policy:
allow:
and:
- domain:
is: your-domain.com
mcp:
server:
path: /mcp
upstream_oauth2:
client_id: OAUTH-CLIENT-ID
client_secret: OAUTH-CLIENT-SECRET
scopes: ["https://www.googleapis.com/auth/file.readonly"]
endpoint:
auth_url: "https://accounts.google.com/o/oauth2/v2/auth"
token_url: "https://oauth2.googleapis.com/token"
timeout: 120s