# Nell > Nell turns a brief and a few links into listenable, AI-generated audio shows and episodes. Nell is in private beta; accounts are invite-only. ## For agents Nell's public setup website is agents.nell.ai. It is not an AI client or the MCP endpoint. Use the MCP server below to read or create content. - [MCP endpoint](https://mcp.nell.ai/mcp): Streamable HTTP. OAuth with PKCE; an approved client's connection opens Nell sign-in. - [Setup and tool inventory](/mcp): per-client configuration and every tool with its read/write access. - [Agent entrypoints](https://mcp.nell.ai/llms.txt): the MCP server's own index. - [Full agent instructions](https://mcp.nell.ai/llms-full.txt): tool contract, error contract, and the safe generation sequence. - [Compatibility manifest](https://mcp.nell.ai/agent-compatibility.json): protocol version, capability profiles, and document digests. Add it to a client with: claude mcp add --transport http nell https://mcp.nell.ai/mcp ## Instructions for Large Language Model agents - Nell researches the brief. Optional source_refs uploads take {filename,content} for .md/.txt (100000 UTF-8 bytes/file), not local paths. Agent-only nell.feedback.submit is optional; never relay a survey or private content. - Reuse saved connectors and protected host OAuth storage; never tokens in chat or skills. Let the client refresh/save rotated tokens. MCP session IDs are not authorization. Claim reuse only after fresh-session identity succeeds; otherwise say unverified. See full recovery instructions. - If already connected, verify with `nell.identity.get` and continue the user's task. Otherwise ask only what is missing: do they have a registered Nell account, an invitation to finish, or need beta access? - Existing users sign in through the client's OAuth flow with their already registered, invited email and sign-in method. Do not ask for passwords, codes, or tokens in chat. An invited user without an account must finish their invitation's account setup first. Users without an invitation can [request beta access](/waitlist); joining the waitlist does not create an account or grant access. - OAuth client registration registers the connecting app, not a Nell user. An `invalid_client` error about approved public clients can block login before any email is checked. Inviting an email does not fix that error: the client owner needs its exact callback URLs reviewed by Nell. Read the full agent instructions for supported clients and recovery; do not invent a contact or claim an escalation was sent. - Keep the user's Nell request and resume it after connection. Do not replace it with unrelated media generation unless asked. - Connect to the MCP server rather than reading this site. The server returns structured results and typed errors; the website returns rendered HTML intended for people. - Use the `https://mcp.nell.ai` origin exactly. Nell's protected-resource metadata declares `https://mcp.nell.ai` as the resource, so connecting through nell.ai instead produces an OAuth resource mismatch. - Use the connected server's advertised tools and permissions. Sources must be absolute HTTPS URLs; local files are not supported over MCP. Use the Nell CLI for local files. - Start a configured `nell.show.create` draft with the user's `idea` and a UUID v4 `idempotency_key`; title and editorial preferences are optional. Relay Nell's questions, review the draft, then confirm the exact reviewed snapshot only after approval. Direct mode requires explicit delegation in the original request. Verify success before claiming creation. - Every creation takes an idempotency key. A timeout or a bounded wait that ends early is progress, not permission to resubmit. - Use validated user input and Nell-generated drafts for product details; relay questions Nell returns. Missing optional preferences do not block starting a draft. ## Optional - [Nell](https://nell.ai): the product itself.