Skip to content

Connect iiiftools to coding agents

iiiftools is a standard remote MCP server over streamable HTTP with OAuth 2.1, so any MCP-capable coding agent can use it. The server URL is the same everywhere:

You’ll need an iiiftools account. The first connection opens a browser to authenticate.

Add the server (HTTP transport), then authenticate:

Terminal window
claude mcp add --transport http iiiftools https://iiiftools.pangur.io/mcp

Inside a session, /mcp lists the server and runs the OAuth browser flow; or use the CLI:

Terminal window
claude mcp list # shows which servers need authentication
claude mcp auth iiiftools # opens the browser to complete OAuth

Remote & headless sessions (SSH, containers)

Section titled “Remote & headless sessions (SSH, containers)”

A locally-added MCP server authenticates via a loopback http://localhost:<port>/callback redirect — which fails when the agent runs on a remote box (the browser is on your laptop, the listener is on the server). Options:

  1. Headless login — have the agent print the authorization URL instead of opening a browser, complete sign-in on your own device, and paste the full redirect URL back.
  2. Use the claude.ai connector instead — a connector added to your claude.ai account is account-bound (no localhost callback) and works over SSH unchanged.

Any client supporting streamable HTTP MCP + OAuth 2.1 discovery (Cursor, VS Code MCP, etc.) can connect with just the URL. OAuth metadata is served at https://iiiftools.pangur.io/.well-known/oauth-protected-resource; clients register themselves via Dynamic Client Registration.

Unlike sandboxed chat apps, coding agents can usually fetch URLs — so prefer delivery="url": the signed links carry full-resolution images without inflating the conversation context, and get_page_range hands back ten at a time.