dot bridge
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
dot bridge
An MCP bridge your dot deploys into its own private Site. Your dot calls any HTTPS API through it: you add the service and its key on the bridge's setup page once, and from then on the dot sends requests with that key.
The bridge is only a bridge. It sends the method, path, query, headers and body your dot gives it to the service's origin, adds the saved key, and returns the response. It does not judge paths, list paths or filter names. The service at the other end decides what each request may do.

Start here
Give your dot the build instructions and ask it to build your bridge.
Setup guide: first deployment, adding a service, updating.
Cookiejar publishing sample: a small static site to deploy.
Source: rkz211/dot-bridge. The version is in
package.jsonand in the MCPinitializeresponse (serverInfo.version).
Related MCP server: lunge
Add a service
Open the bridge's private page and choose New service.
Enter a name, an HTTPS endpoint the bridge can GET to check the key, and the key.
Choose Save & test. The key is saved when the check passes.
The default header is Authorization: Bearer <key>. Authentication options also offers X-API-Key and any custom header and prefix. The endpoint's origin becomes the service's base URL. Your dot can also prepare a service from the provider's documentation with bridge_prepare_connection; you then add the key on the page.
Cookiejar is built in. Use your account key (sites_…); the page checks it with GET /sites.
Tools
Tool | What it does |
| Shows the Sites-managed sign-in status and the signed-in user ID |
| Adds a service: origin, auth header, prefix, description |
| Lists services, whether each has a key, and setup links |
| Lists services and whether each has a key |
| Shows the request the bridge would send, without sending it |
| Sends GET or HEAD and returns the response |
| Sends POST, PUT, PATCH or DELETE and returns the response, recorded under a UUID |
| Uploads source bytes to the signed Cookiejar source URL from |
| Shows the recorded outcome of a write |
| Lists the Cookiejar sites the saved key owns |
| Creates a Cookiejar site |
| Deploys a source ZIP to a Cookiejar site and starts the build |
| Shows the recorded outcome of a create or deploy |
Any path on the service works. There is no endpoint map to maintain: the dot reads the service's own documentation and sends the request.
How it works
Requests always go to the saved origin of the service named by
serviceId, with the saved auth header and key. A request cannot change the origin or the auth header.Redirects are returned as
redirectRefusedinstead of followed, so the key never travels to another host.The bridge removes its own saved key values from responses and errors. Everything else in the response passes through unchanged.
Each write is recorded under its
operationId. Sending the same ID again returns the recorded result instead of repeating the write.Keys are saved in the Site's own D1 database and are never shown again on the page.
The Site is owner-private. Sites-managed sign-in identifies the caller.
Development
Node.js 22.13 or later (Node.js 24 recommended). No runtime dependencies.
npm test
npm run check
npm run buildnpm test regenerates ui.mjs from ui/ first. The build writes the Worker and its modules to dist/server/.
License
MIT. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Call third-party APIs from agents without leaking secrets. SSRF blocked, per-key quotas.
Create, update, and publish real hosted websites from your agent via the Aveiro API.
Let agents make HTTP requests later: schedule, retry, cron, watch jobs, receive webhooks.
Host any HTTP API as MCP tools with a tamper-evident cross-agent settlement ledger.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to send HTTP requests to any endpoint with full control over methods, headers, query parameters, and request bodies.1MIT
- FlicenseNot gradedqualityCmaintenanceAgent-native API client for executing REST, GraphQL, WebSocket, SSE, and gRPC requests from MCP-capable agents, with token-efficient responses and file-based collections.-
- AlicenseNot gradedqualityBmaintenanceEnables importing OpenAPI, Swagger, Google Discovery, GraphQL, and HTTP MCP definitions and generating typed agent tools whose calls map to HTTP endpoints under explicit execution policies such as allow, approval, or block. A hosted runtime adds credentials, OAuth scopes, request validation, approvals, and execution traces for safely exposing those endpoints to agents.20 npm4MIT
- AlicenseAqualityCmaintenanceEnables AI agents to execute HTTP/REST/GraphQL requests against any endpoint, including private VPN hosts and local services, while logging untruncated headers, request bodies, and raw responses into a local SQLite audit history. Agents can then search that history by keyword, date, method, or status, retrieve full details by ID, and export everything to JSON.5MIT