Skip to content

docs(readme): note the sign-in step the claude mcp add one-liner needs#11019

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-elon merged 1 commit into from
Aug 22, 2026
Merged

docs(readme): note the sign-in step the claude mcp add one-liner needs #11019

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions .changeset/readme-mcp-add-auth.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
---
"@objectstack/spec": patch
---

docs: note that the root README's `claude mcp add` one-liner needs a follow-up sign-in step (#10319)

The "Your app is AI-operable, for free" section's copy-paste command
(`claude mcp add --transport http my-app http://localhost:3000/api/v1/mcp`)
registers the server correctly, but running it alone and then calling a tool
401s — measured live, at head, against a freshly booted `examples/app-crm`:
unauthenticated `initialize` returns
`401 {"code":"UNAUTHENTICATED","message":"Unauthorized: a valid OAuth access
token or API key is required"}`, exactly as the finding this closes reported.
The README gave no hint that a sign-in step follows the command.

The linked docs page, [Connect an MCP
Client](https://objectstack.ai/docs/ai/connect-mcp), already carries the step
in full (interactive OAuth browser login, plus a headless API-key flow for
CI/containers) — confirmed by reading it and by reproducing both paths live:
the same unauthenticated call 401s with a `WWW-Authenticate` header
advertising OAuth metadata, and minting a key via `POST /api/v1/keys` with a
session cookie and sending it back as `x-api-key` returns `200` with a valid
`initialize` response. So the fix is a one-sentence pointer in the README, not
a rewrite of the docs page it already correctly delegates to.
7 changes: 5 additions & 2 deletions README.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -172,8 +172,11 @@ as a human:
claude mcp add --transport http my-app http://localhost:3000/api/v1/mcp
```

Objects are exposed automatically; actions opt in with `ai: { exposed: true }`.
See [Connect an MCP Client](https://objectstack.ai/docs/ai/connect-mcp).
The first tool call opens a browser to sign you in — each deployment is its own
OAuth server, so there's no token to copy-paste. Headless setups (CI,
containers) use an API key instead. Objects are exposed automatically; actions
opt in with `ai: { exposed: true }`. See
[Connect an MCP Client](https://objectstack.ai/docs/ai/connect-mcp) for both flows.

## This repo

Expand Down
Loading