PDF Server (MCP Apps example)
modelcontextprotocolLABSCO SUMMARY
The selling point is negative — the AI platform never sees your credentials.
OAuth against the vendor means the token belongs to the connection, not to whatever client you happened to use, and revoking it in one place actually revokes it. For a document store holding contracts and statements, that boundary is worth more than any tool in the list. Dynamic registration means you get it without filing a developer application first.
What it is
pdfAssistant's hosted endpoint, connected to the same account you use in their web app. Their own pitch for it is that the credentials stay with them and are never handed to the AI platform.
What you get
Your document library reachable from the conversation, so an assistant can read and answer against files you have already uploaded rather than needing them re-attached each time.
Requirements
OAuth 2.0 with dynamic client registration — a compliant client discovers the authorisation server itself. A paid plan is needed; the integration is included on every paid tier rather than sold separately.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Asking about a document you already uploaded
The library is reachable from the chat, so nothing needs re-attaching.
02
Keeping the sign-in off the AI platform
OAuth against pdfAssistant, revocable from your account.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.0 Bearer, dynamic client registration
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://chat.pdfassistant.ai/mcpRequirements
- OAuth 2.0 Bearer, dynamic client registration
