How do I connect the Nicelydone MCP server?

The Nicelydone MCP server connects compatible AI clients to the design library.

The server uses browser-based OAuth. You do not need a separate API key.

If you connected with https://nicelydone.club/mcp-server, that address still works. New connections should use https://mcp.nicelydone.club/mcp. To switch an existing Claude Code connection, run:

claude mcp remove nicelydone
claude mcp add --transport http nicelydone https://mcp.nicelydone.club/mcp

Then run /mcp inside Claude Code and sign in again.

Open the setup page

Visit the MCP setup page. Select your client to see its current setup instructions.

The page includes instructions for clients such as Claude Code, Claude Desktop, Cursor, Lovable, ChatGPT, Codex, Windsurf, VS Code, and Zed.

Add the server

Use the native remote MCP connection when your client supports it. The hosted server address is shown on the setup page.

Some older clients use mcp-remote as a compatibility bridge. Copy the configuration shown for your client instead of adapting another client’s example.

Authorize your account

Your browser opens when the client first connects or calls a Nicelydone tool. Sign in to Nicelydone and approve the connection.

MCP access requires an eligible paid plan.

Choose permissions

The consent screen lists the permissions requested by your client:

• library:read: Search the design library and read screen details.
• saved:read: Read your favorites and collections.
• collections:write: Create and update collections and add screens.

Requests without a scope receive library:read. To use saved content or change collections, request the matching scope and approve a new connection.

Connections created before scoped consent was introduced must reconnect. Old tokens do not grant access.

Use the paid MCP API

The OpenAPI specification describes the MCP endpoint. The machine-readable setup guide describes client registration and OAuth.

MCP requires a paid account and uses the OAuth resource https://mcp.nicelydone.club/mcp. App browser routes are not an external API.

Use browser tools

Compatible browsers expose screen search and collection tools when you sign in to a paid account. The Create collection form requires you to review and submit the action.

Test the connection

Ask your client a focused question, for example:

Find onboarding flows that include email verification and a team invitation.

If the client cannot connect, make sure that you are signed in. Reconnect the server.

Make sure that the server address matches the address on the MCP setup page.