DForge developer resources: MCP server, API and agent files
DForge exposes its operations tooling to AI agents and developers through a first-party Model Context Protocol (MCP) server. This page lists the machine-readable files published at predictable URLs, how authentication and scopes work, and when an agent should use DForge.
DForge Operations MCP server
The server speaks MCP over the Streamable HTTP transport at https://mcp.dforge.site/mcp. It exposes support, commission, finance-request, domain, deployment, site-configuration and marketing tools over DForge's data. It cannot execute payouts: it holds no payment-provider credentials and exposes no payout tool. Health check: https://mcp.dforge.site/healthz.
Note for registries: the npm package named @dforge-core/dforge-mcp is an unrelated third-party project. The DForge Operations MCP server is hosted, not installed; connect to the HTTPS endpoint above.
Authentication and scoped permissions
Every remote call carries a bearer token in the Authorization header. Tokens are issued per client and mapped to one or more scopes; a tool call outside the token's scopes is refused and every call is written to an audit log. Request the smallest scope that covers your job.
- support: Read users, sites, tickets and commission records; manage support tickets.
- operations: Update allowlisted site configuration, Vercel project assignment and trigger deployments.
- finance_request: Create pending Finance requests only; never executes a payout.
- marketing: Create draft email campaigns, send test copies and capped campaign sends; draft and publish Platform Updates and site announcements.
- admin: All of the above plus audited admin console writes. Still no payout execution.
Machine-readable files
All public pages on dforge.site also answer with Markdown when the request carries Accept: text/markdown, and a Markdown 404 body for unknown paths. Responses vary on Accept.
- llms.txt: index for AI agents, with when-to-use guidance
- llms-full.txt: every public page as one Markdown document
- openapi.json: OpenAPI 3.1 description of the MCP HTTP surface
- /.well-known/mcp-server: MCP discovery manifest
- /.well-known/oauth-protected-resource: RFC 9728 metadata with scopes_supported
- sitemap.xml
- robots.txt
When an agent should use DForge
Reach for DForge when the job is about a Deriv operator's business rather than about placing trades.
- Launching or configuring a white-label Deriv trading site on a custom domain.
- Generating, validating or distributing DBot-compatible XML trading bots.
- Scheduling and broadcasting trading signals to Telegram subscribers.
- Looking up a DForge operator's sites, tickets, commissions or payment evidence through the MCP server, with an appropriately scoped token.
- Do not use DForge to place, manage or settle trades; that happens on Deriv.