dpf-mcp-bridge

A stdio MCP server that mirrors DPF's tool surface for clients that can't speak Streamable HTTP or do an OAuth redirect — most notably registry crawlers (e.g. Glama) that need to see tools/list without an interactive login.

Most users don't need this. Claude, Cursor, VS Code, and other OAuth-aware MCP clients should connect directly to the real server at https://api.dpf-it.com/mcp — see the integration guide or the dpf plugin in this repo. This bridge exists for stdio-only clients and for directory listings.

How it works

• initialize / tools/list are answered locally from schemas declared in server.js — no network call, no credentials required. That's what lets an automated sandbox introspect this server.

• tools/call forwards to the live endpoint (DPF_MCP_URL, defaults to https://api.dpf-it.com/mcp) with Authorization: Bearer $DPF_TOKEN. Without DPF_TOKEN set, calls return an explanatory error instead of failing silently.

Run it

DPF_TOKEN=<your OAuth access token> npx dpf-mcp-bridge

or with Docker:

docker build -t dpf-mcp-bridge .
docker run -i -e DPF_TOKEN=<your OAuth access token> dpf-mcp-bridge

Obtain a token via the OAuth flow described in the integration guide, or self-serve a client_id/client_secret pair (POST /oauth/clients) and exchange it for an access token via the standard OAuth token endpoint.