Nooks

Agent on-ramps · MCP

Connect your agent to Nooks.

Your agent builds with real brick parts inside a Nooks build. It checks the structure, saves revisions you can edit, and hands back a manual and a parts list.

Open the Connect dialogDeveloper docs

Sign-in is OAuth: your client opens Nooks, you approve one build, and no key is pasted anywhere. The workbench dialog is the live flow; this page is the reference for every supported client.

1. Choose what your agent can see

MCP profile

MCP address https://nooks.place/api/mcp

All three profiles accept the same OAuth grant. The build surface is the 59 tools a customer job needs; the core profile is the lean 13-tool authoring loop; the full profile adds the benchmark, brief, contribution and real-place tools.

2. Add it to your client

Each card names the file the client reads and the command that writes it. Change the profile above and every command and file on this page follows. A client that is only "documented" here is supported by its own docs; "preview" means Nooks has not validated it yet.

Claude Code

Documented by the client
Config
~/.claude.json for every project, or .mcp.json in one project
Add it
claude mcp add --transport http --scope user nooks https://nooks.place/api/mcp

The CLI can write this file for you below.

Sign in
claude — run /mcp, choose nooks, then Authenticate

A remote HTTP server needs "type": "http" in Claude Code's file. The command above, and this CLI, write it.

The file, if you prefer to write it yourself 
{
  "mcpServers": {
    "nooks": {
      "type": "http",
      "url": "https://nooks.place/api/mcp"
    }
  }
}

Connect in the workbench → Client docs

Codex

Sign-in tested by Nooks
Config
~/.codex/config.toml
Add it
codex mcp add nooks --url https://nooks.place/api/mcp

The CLI can write this file for you below.

Sign in
codex mcp login nooks

Codex keeps the OAuth credential itself, so no token goes in the file.

The file, if you prefer to write it yourself 
[mcp_servers.nooks]
url = "https://nooks.place/api/mcp"

Connect in the workbench → Client docs

Cursor

Documented by the client
Config
.cursor/mcp.json in this project, or ~/.cursor/mcp.json
Add it

Add the server in Cursor's MCP settings, or write the file below.

Sign in
in Cursor, open Settings, then MCP (or Tools & Integrations), select nooks and choose Connect

Cursor reads the same mcpServers shape and handles the OAuth sign-in in its own window.

Add the Nooks server to Cursor →

The link pre-fills the server address; Cursor still opens the Nooks sign-in and consent screen.

The file, if you prefer to write it yourself 
{
  "mcpServers": {
    "nooks": {
      "url": "https://nooks.place/api/mcp"
    }
  }
}

Connect in the workbench → Client docs

OpenClaw

Documented by the client
Config
~/.openclaw/openclaw.json
Add it
openclaw mcp add nooks --url https://nooks.place/api/mcp --transport streamable-http --auth oauth

The CLI can write this file for you below.

Sign in
openclaw mcp login nooks

OpenClaw stores servers under mcp.servers and wants transport: "streamable-http" spelled out; without it it falls back to SSE.

The file, if you prefer to write it yourself 
{
  "mcp": {
    "servers": {
      "nooks": {
        "url": "https://nooks.place/api/mcp",
        "transport": "streamable-http",
        "auth": "oauth"
      }
    }
  }
}

Connect in the workbench → Client docs

Hermes

Preview: not yet validated
Config
~/.hermes/config.yaml
Add it

Add the server in Hermes's MCP settings, or write the file below.

Sign in
hermes mcp login nooks

Hermes reads mcp_servers from ~/.hermes/config.yaml and keeps OAuth tokens in ~/.hermes/mcp-tokens. Its optional-MCP manifest is prepared, not submitted, and is unvalidated against Hermes 0.23.

The file, if you prefer to write it yourself 
mcp_servers:
  nooks:
    url: https://nooks.place/api/mcp
    auth: oauth

Connect in the workbench → Client docs

Grok Build

Preview: not yet validated
Config
~/.grok/config.toml
Add it
grok mcp add nooks --url https://nooks.place/api/mcp

The CLI can write this file for you below.

Sign in
grok mcp login nooks

Grok Build uses the same TOML mcp_servers shape as Codex. Its command names, and whether Grok Bot can reach Nooks from chat, are still untested.

The file, if you prefer to write it yourself 
[mcp_servers.nooks]
url = "https://nooks.place/api/mcp"

Connect in the workbench → Client docs

Grok Bot and other chat apps

A chat app that can add remote MCP servers can add Nooks from the prompt alone. Paste this into the chat; it does not contain a credential. Whether Grok Bot can reach Nooks from a chat is still untested — the prompt is here so the test is one paste.

Connect to the Nooks MCP server at https://nooks.place/api/mcp using OAuth. Open the Nooks sign-in link and let me approve access to one build, then call list_builds to confirm the connection. After that, help me design a custom brick set from my photo: read runtime_guide, build with build_program, check with check_model, and never say the model is buildable unless check_model passes. Do not ask me for a token; if this chat cannot add a remote MCP server, say so and give me the config file for my client instead.

If the app cannot add a server itself, it will ask for a config file; use that client's card above.

3. Or let the CLI write the file

nooks-mcp detects the clients on your machine, prints a plan, and writes only the address. It never stores a token, and it will not overwrite an existing nooks entry without --force.

npx --yes nooks-mcp init --dry-run
npx --yes nooks-mcp init --yes
npx --yes nooks-mcp init --client codex --full
npx --yes nooks-mcp init --force

Published on npm as nooks-mcp 0.1.1. It writes only the MCP address; sign-in is OAuth, and no token is stored.

No dependencies, no network calls, and the tests use fixture home directories.

For tools that discover servers

Server card: /.well-known/mcp/server-card.json. Registry name: place.nooks/nooks (prepared, not submitted). The streamable HTTP address is https://nooks.place/api/mcp.