Hosted MCP server/Productivity

iFillPDF MCP server

Hosted at mcp.ifillpdf.com·Streamable HTTP

iFillPDF fills and signs PDFs from the Gemini CLI or a remote MCP client. AI field detection works on any document, including scanned forms. The canonical install is the Gemini CLI extension, gemini extensions install https://github.com/machouz/ifillpdf-gemini-extension. Remote clients use https://mcp.ifillpdf.com/mcp with OAuth 2.1 and PKCE: the browser sign-in is discovered automatically, there is no API key to paste, and no config file to edit. The flow has not been independently connection-tested here.

mcp.ifillpdf.com Streamable HTTP OAuth 2.1 with PKCE (browser sign-in; no API key) Server not checked yet Reviewed 2026-11-16
About

Where it fits

People who fill and sign PDF forms, especially scanned documents that need automatic field detection.

  • Install the Gemini CLI extension.
  • Fill a scanned PDF with detected fields.
  • Sign a completed PDF after review.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Gemini CLI extension

This is the provider's canonical install. Remote HTTP clients can point at https://mcp.ifillpdf.com/mcp and complete OAuth 2.1 with PKCE in the browser; no API key or config file is needed.

  1. Install the Gemini CLI extension

    Run the provider's canonical extension install command.

    gemini extensions install https://github.com/machouz/ifillpdf-gemini-extension
  2. Or connect a remote client

    Add https://mcp.ifillpdf.com/mcp as a remote MCP server. The client discovers OAuth 2.1 with PKCE and opens a browser sign-in on first use; there is no API key to paste.

  3. Fill and sign

    Ask the client to fill a PDF. Field detection runs on the document, including scanned forms, and you approve the result before signing.

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://mcp.ifillpdf.com/mcp
Host
mcp.ifillpdf.com · /mcp
Transport
Streamable HTTP
Authentication
OAuth 2.1 with PKCE (browser sign-in; no API key)
Server name
ifillpdf
Listing type
Community or directory listing

The installer uses the server name ifillpdf. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that ifillpdf appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Install the Gemini CLI extension. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

iFillPDF repositoryhttps://github.com/machouz/ifillpdf-gemini-extension