TL;DR: In Lovable, open Connectors, click + and choose MCP server. Name it Noded, enter the URL https://app.getnoded.ai/api/mcp/apps, keep OAuth, click Add & authorize and sign in with your Noded account. Noded is then available in the project chat (build) and in Chats. Reads are read-only. Every write (an email, a message, a note, a CRM record, a workflow run) arrives as a recommendation that you approve or dismiss.
This connection gives Lovable context while you work. It does not reach a published app. If you are building an app that itself runs on Noded data, the connector is step one of three - see Build with Lovable for the Workspace Setup and App Builder skills that take it from there.
What you need
- A Noded account with data connected. Lovable can only find what Noded has synced. Connect at least one source (Gmail, Slack, a calendar, a call recorder, or a CRM) in the Noded app first.
- A Lovable workspace. Custom MCP servers are available on every Lovable plan and are on by default. A workspace admin can switch them off under Connectors → Admin settings → Chat connectors; if the MCP server option is greyed out when you click +, that is why. See Lovable’s custom MCP guide for the current details.
- The server URL.
https://app.getnoded.ai/api/mcp/apps- enter it exactly, including the path. Lovable registers itself with Noded’s sign-in service automatically; you do not need a client ID or secret.
Who can set this up?
| Your Lovable workspace | Who adds the Noded server | Who signs in to Noded |
|---|---|---|
| Personal, or a team with custom MCP left on (the default) | You, from Connectors. No admin involved. | You, once, when you add it. |
| A team where an admin has turned custom MCP off | An admin re-enables Allow members to connect their own MCP servers under Connectors → Admin settings → Chat connectors, or lists Noded in the workspace’s MCP registry so members connect it from the catalog. | Each member, individually - connections are per user, so everyone sees only their own Noded data. |
In short: by default everyone self-serves; an admin switch is only involved if your workspace has turned custom servers off.
Using another assistant? See the guides for Claude, ChatGPT, Gemini, Microsoft Copilot Studio, and Slackbot.
Connect Noded in Lovable
1️⃣ Open Connectors. From the Lovable dashboard, open Connectors, click the + button at the top right of the catalog and choose MCP server.
2️⃣ Fill in the server.
| Field | Value |
|---|---|
| Server name | Noded |
| Connection | Direct connection, if the dropdown appears. (Lovable static IPs is an Enterprise option and is not needed for Noded.) |
| Server URL | https://app.getnoded.ai/api/mcp/apps |
| Authentication | OAuth (the default) |
3️⃣ Sign in to Noded. Click Add & authorize. A Noded sign-in window opens. Use the same email address as your Noded account, then approve the requested access. The consent screen lists read access to your customer context and the ability to create recommendations for you to review.
4️⃣ Test with a read. In a project chat or in Chats, ask: “Using Noded, what can you do?” Lovable calls Noded and lists the built-in actions plus the searches, workflows, and record types installed for your account. Then try “When did we last talk to Acme, and is anyone waiting on a reply from us?”
5️⃣ Build with it. In a project, Lovable can now read your real accounts, people and activity while it writes code - so a dashboard mock-up is seeded with the shape of your actual data, and a prompt such as “show me which record types my Noded workspace has” gets a real answer. If the project is an app that should run on Noded in production, continue with Build with Lovable.
Where it works, and where it does not
Custom MCP servers give Lovable context in two places: the project chat, while you build, and Chats, Lovable’s standalone assistant. They do not run inside your published app - the app has no connection to Noded unless you build one. That is deliberate on Lovable’s side, and it is why the App Builder skill generates server-side calls to the Noded Graph API with a personal access token held as a server secret, rather than reusing your chat connection.
What Lovable can do with Noded
Noded exposes one connector with a small set of capability groups. You never need the tool names; describe what you want and Lovable picks the right one.
| Group | What it does | Example prompt |
|---|---|---|
| Find people and accounts | Resolves a name or company to the right contact or account, lists related people (buying committee, who else is involved), and reads your saved folders such as My Accounts. | “Who else at Acme has been on our calls?” |
| Read activity | Emails, chat messages, meetings and transcriptions, notes, tasks, and saved CRM or support records - filtered by person, account, date, direction, or status. Semantic search finds themes when exact filters are not enough. | “What was decided on the last two Acme calls?” |
| Check engagement | Per-account activity across every channel in one call, and unanswered emails - who is waiting on you, and who has gone quiet. | “Which of my accounts have gone quiet this month?” |
| Search connected apps | Read-only live lookups in the apps you have connected (Salesforce, HubSpot, Zendesk, Jira, Linear, and others) using the searches installed for your account. | “Find open Zendesk tickets for Acme.” |
| Draft and act | Draft an email, a Slack or Teams message, or a note; create a record in a connected system (a Jira issue, a Salesforce case, a HubSpot record); or run one of your installed workflows. Each one arrives as a recommendation to review. | “Draft a follow-up to Jane at Acme about next steps.” |
| Workspace setup | Read and change your Noded configuration - insights, tables, folders, record types and agents - by conversation. This is what the Workspace Setup skill drives, and what the App Builder skill reads to learn what your workspace contains. | “Set up my Noded workspace for my business.” |
| Dates | Helpers for the current time, relative dates, and date arithmetic so questions such as “in the last 10 days” resolve correctly. | “How many days until the Acme renewal?” |
The exact list of searches, workflows, and record types is specific to your account. It depends on which apps you have connected in Noded and which queries and functions your team has installed. Ask “Using Noded, what can you do?” at any time to see the current list.
How the review step works
Noded separates reading from writing. All the read tools are read-only. Every write goes through a recommendation:
1️⃣ Lovable proposes. When you ask for an email, a message, a note, a record, or a workflow run, Lovable composes the proposal and asks Noded to create a recommendation. Nothing is sent, saved, created, or run at this point.
2️⃣ You review it. The recommendation is waiting in the Noded app - the recipients, the subject and body, the record fields, or the workflow inputs. You can edit the text before you decide.
3️⃣ Approve or dismiss. Approve accepts the recommendation with your edits, and Noded carries it out through the connected system. Dismiss discards it. Lovable reports the result only after Noded confirms it.
Recommendations are visible in the Noded app, so a teammate with access can also review them there. If Noded cannot create a recommendation, Lovable tells you so instead of pretending the action happened.
Permissions and data handling
- The connector runs as you. Lovable sees only what your Noded user can see. Tenant boundaries and sharing permissions are the same as in the Noded app.
- Sign-in is OAuth 2.1 with PKCE. Lovable never holds your Noded password. The token is scoped to reading your customer context and creating recommendations.
- Chat only. The connection never reaches a published app, so nothing you build can read Noded through it by accident. An app that should run on Noded gets its own credential - a personal access token, server side - as described in Build with Lovable.
- Disconnect at any time. Remove the server under Connectors. Access ends for your Lovable account immediately.
- Nothing new is stored in Lovable by Noded. Query results are returned to the chat you are in and are governed by Lovable’s data policy.
Troubleshooting
- MCP server is greyed out when you click +. A workspace admin has turned off custom MCP servers. Ask them to re-enable Allow members to connect their own MCP servers under Connectors → Admin settings → Chat connectors, or to list Noded in the workspace registry.
- Add & authorize fails. Check that the server URL is exactly
https://app.getnoded.ai/api/mcp/apps, including the path, and that Authentication is OAuth. Lovable registers itself; there is no client ID or secret to enter. - “Unauthorized” or the server shows as disconnected. Sign in with the same email address as your Noded account. If you have more than one Noded workspace, use the one you want Lovable to read.
- Lovable says Noded tools are unavailable. The server was added after the chat started, or is not attached to this workspace. Start a new chat; if it persists, remove and re-add the server.
- Lovable finds nothing for an account you know is active. Check that the source (email, calendar, Slack, call recorder, CRM) is connected in Noded and has finished its first sync.
- Lovable answers from general knowledge instead of Noded. Say “using Noded” in the prompt.
- My published app cannot see Noded. Expected - custom MCP servers work in the chat only. Follow Build with Lovable to give the app its own server-side connection.
FAQ
Do I need an admin to set this up?
Usually not. Custom MCP servers are on by default on every Lovable plan, so you add Noded yourself from Connectors. An admin is only involved if your workspace has switched custom servers off. See who can set this up.
Do I need a client ID and client secret from Noded?
No. Lovable registers itself with Noded’s sign-in service automatically (dynamic client registration), so you keep OAuth selected, paste only the server URL and click Add & authorize.
Does this make my Lovable app run on Noded?
No. The connection is for the project chat and Chats - it helps Lovable understand your customer data while you build, and lets you ask Noded questions. A published app needs its own server-side connection to Noded; the App Builder skill generates it.
Can Lovable send an email or create a record through Noded without asking me?
No. Every write becomes a recommendation. Nothing is sent, saved, created, or run until you approve it in Noded.
Which URL do I paste?
https://app.getnoded.ai/api/mcp/apps, entered exactly, including the /api/mcp/apps path.