Connect SiteForge to your AI assistant

What connecting does

Connecting lets your AI assistant talk to SiteForge directly, so you can ask for a website in your own words instead of building one by hand.

The assistant reserves a draft site for you and asks what you want it to be. You claim the draft with your account, and then the assistant builds it. You connect once; after that, naming SiteForge is enough.

Once connected, you can say something like:

Reserve me a site called example-site on SiteForge, then interview me about what it should be.

Reserving comes first and costs nothing: it gives you a named draft and a link to claim it. A draft is never published, and reserving one does not let the assistant build anything until you have claimed it with your account.

Your assistant is asked to pass an automated challenge check when it reserves. It handles that itself — there is nothing for you to solve.

The address to connect to

This is the address your assistant needs. Every set of instructions below already contains it.

https://fedcanvas.be/mcp/rpc

What you will be asked to approve

Your assistant introduces itself to SiteForge on its own, then sends you to a sign-in page here. You sign in, look at what the assistant is asking for, and approve it. There is no key to generate and nothing to paste back.

Unless your assistant asks for something narrower, it asks for mcp:* — everything SiteForge offers, which is 70 named permissions. The approval screen lists what you are approving before you approve it, and you can refuse.

Find your assistant

Claude Code, and other assistants you run in a terminal

Run this where you run the assistant. It adds SiteForge, and the first time you use it your browser opens so you can sign in and approve.

claude mcp add --transport http siteforge https://fedcanvas.be/mcp/rpc

Claude, and other assistants that take a custom connector

Open the assistant's settings and find where it lists connectors or external tools. Add a custom one, and give it this address:

https://fedcanvas.be/mcp/rpc

The assistant sends you to SiteForge to sign in and approve. Your assistant's own documentation names the settings screen.

Cursor, VS Code, and other code editors

Editors that support this keep a JSON file listing the servers they can reach. Add this entry to it — your editor's documentation names the file and where it lives:

{
    "mcpServers": {
        "siteforge": {
            "url": "https://fedcanvas.be/mcp/rpc"
        }
    }
}

Reload the editor. It sends you to SiteForge to sign in and approve the first time it connects.

An assistant that can only run a program on your computer

Some assistants cannot call a web address at all — they can only start a program locally. A small bridge called mcp-remote is that program: it runs on your computer, passes everything to SiteForge, and opens your browser for the sign-in step. Add this to the assistant's configuration file:

{
    "mcpServers": {
        "siteforge": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-remote",
                "https://fedcanvas.be/mcp/rpc"
            ]
        }
    }
}

The bridge is downloaded and run by npx, so Node.js has to be installed on your computer.

Scripts, and anything not listed here

Anything that can send an HTTP request can use SiteForge. This asks it which tools it offers; put the access token from the approval step in place of the placeholder:

curl -sS -X POST https://fedcanvas.be/mcp/rpc \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The machine-readable description of this server is at https://fedcanvas.be/.well-known/mcp.json, and the full guide for assistants is at https://fedcanvas.be/AGENTS.md.

Assistants that cannot connect

Not every assistant can attach an outside tool source. Asked to build a website on SiteForge, these three did not connect: the ChatGPT chat interface, Google Gemini, and Microsoft Copilot. This platform's own access log shows what they did instead: one fetched public documentation only, and two sent no request at all.

The reason is the same in each case. They have no way to send SiteForge the kind of request its tools need, so there is nothing on this page for you to paste into them.

Two of them did something worse than refuse: they never looked at SiteForge at all. Both invented a company from the domain name and produced a website for a business that does not exist. If an assistant hands you a finished site without ever asking you to connect anything, that is what has happened.

Whether any of them gains the ability to connect is their decision and not ours, so this page makes no claim about it.

What works instead: build your site here in your browser. Start a site in the browser. You can connect an assistant afterwards and point it at the site you already have.