Nodaro Docs
DocumentationNode ReferenceModelsAI Agents (MCP)DevelopersSelf-hostingResearch
Connect a client

Connect a client

Connect Claude, ChatGPT, VS Code, Cursor, Cline, Continue, Goose or any MCP client to Nodaro with one server URL and a short OAuth sign-in.

To connect a client to Nodaro, you add one URL to your AI assistant and sign in with your Nodaro account. The URL is https://mcp.nodaro.ai/mcp for every client. The whole setup takes about a minute, and after it the assistant can use every Nodaro MCP tool you allowed.

The three steps

Copy the MCP URL

https://mcp.nodaro.ai/mcp

Use it exactly as written, with no trailing slash.

Add a remote server in your client

Open your client's connector or MCP settings and add a remote server with the URL. Choose the Streamable HTTP transport and OAuth sign-in when the client asks. Several clients have a link that opens this step for you; see the table below.

Sign in and authorize

Your browser opens the Nodaro sign-in page. Sign in with your Nodaro account, review the permissions on the consent screen, and click Allow. The client then shows Nodaro as connected, and the tools appear.

Choose your client

ClientWhere to add the serverOne-click link
ClaudeSettings › Connectors › Add custom connectorOpens the dialog with the name and the URL filled in
ChatGPTSettings › Connectors › Advanced › Developer mode › CreateOpens the create form; you paste the URL
VS CodeCommand Palette › MCP: Add Server › HTTPInstalls the server with everything filled in
CursorSettings › MCP › Add new MCP serverInstalls the server with everything filled in
ClineMCP Servers › Remote ServersNone
Continueconfig.yaml, under mcpServersNone
GooseSettings › Extensions › Add custom extensionAdds the extension with everything filled in
Your own clientAny client with Streamable HTTP and OAuthNone

Other clients

These clients also take a remote MCP server. The steps come from each client's own connector settings.

ClientSteps
LovableOpen Dashboard › Connectors › Add MCP server, or use the Add MCP server link, which opens the dialog without filling it in. Name the server Nodaro, paste the URL, and leave authentication on OAuth. Click Add, authorize, and sign in with Nodaro. The tools appear as a chat connector.
Bolt.newIn the chat box, open the + menu, then Connectors › Manage connectors › Custom MCP server. Paste the URL, choose the HTTP transport and MCP OAuth, and sign in with Nodaro. The tools appear as a Bolt connector.
Base44Open your profile icon, then Settings › Account › MCP connections. Choose Add custom MCP, paste the URL, set authentication to OAuth, and sign in with Nodaro. Custom MCP servers need a Base44 Builder plan or higher.
v0Open Settings › MCP connections › Add MCP, or use the MCP connections link. Choose a custom server instead of a preset, paste the URL, set authentication to OAuth, and authorize with Nodaro.
Grok BotOpen Settings › Plugins and add a custom connector. Paste the URL as the server URL, keep authentication on OAuth, and sign in with Nodaro when Grok asks. On grok.com, the same connector is under Connectors › New Connector › Custom. Grok Bot needs a Cursor Ultra or SuperGrok Heavy plan.
OpenClawIn the Control UI, open Settings › MCP › Add server, name the server nodaro, choose Streamable HTTP and paste the URL. Set the server's authentication to oauth and sign in with Nodaro. You can also add the server from the command line, as shown below.
HermesAdd a nodaro entry under mcp_servers in ~/.hermes/config.yaml, with the URL and auth: oauth. Then run /reload-mcp in a session, or hermes mcp login nodaro, and sign in with Nodaro in the browser.

OpenClaw from the command line: add the server with the first command, and set its authentication to oauth. The second command opens the browser so you can sign in with Nodaro. The third command confirms that the tools load.

openclaw mcp add nodaro --url https://mcp.nodaro.ai/mcp --transport streamable-http
openclaw mcp login nodaro
openclaw mcp doctor nodaro --probe

The Hermes entry in ~/.hermes/config.yaml:

mcp_servers:
  nodaro:
    url: "https://mcp.nodaro.ai/mcp"
    auth: oauth

The consent screen lists the permissions the client asks for, such as reading your workflows, running generations and uploading files. Allow all of them for full access. A tool whose permission you did not grant is hidden from the assistant. Permissions lists which tool needs which permission.

The consent screen also shows the Nodaro account the client connects as. Click Use a different account to sign in with another account. The client name on the screen is chosen by the client itself and is not verified by Nodaro, so check that the app is the one you are setting up.

Check the connection

Ask the assistant: "Call the Nodaro ping tool." The ping tool answers with pong, your Nodaro user id and the name of your client. Then try a real request, for example "Generate an image of a knight with Nodaro."

If the client shows an error, or shows Nodaro as connected but lists no tools, see Troubleshooting.

Frequently asked questions

Last updated on

On this page