Connect an agent

GenBlocks speaks MCP, the protocol agent clients use to call tools. Point a client at the server once and it can search the library, read an item and queue a block or an image. The first call opens this site's consent screen, and the token that comes back can only reach those tools.

Endpoint

https://genblocks-mcp-136956166484.europe-southwest1.run.app/mcp

Production

Streamable HTTP, with OAuth. This page is running on the deployment, so the commands point at its published address.

01Add the server

Pick the client you use. Each one is told about the same endpoint in its own way; the rest of the setup happens on the first call.

Run it in your terminal. Drop --global to register the server for this project only.

opencode mcp add genblocks --global --url https://genblocks-mcp-136956166484.europe-southwest1.run.app/mcp

Run /mcps, pick genblocks and sign in. opencode keeps the token from there on.

opencode documentation

02Approve the first call

The first tool call opens a consent screen on this site. Sign in if you have not already, then approve the request. The token that comes back can only reach the MCP tools, never the REST API, and you can end an agent's access at any time under Profile → Connected applications.

03Ask for something

Then talk to the agent as usual. It can search and read the library, plan a brief, and queue a block or an image; a write returns a task, and get_task follows it to the published result.

“Find a pricing block with three tiers and a dark treatment.”
“Show me the newest photography about stone and water.”
“Build a testimonial section for a two-person studio; no people in the pictures.”

Agents and people see the same library: an agent publishes into the same registry this site shows.