Skip to content

The assistant from Claude and other applications

The AI Assistant doesn’t only live in the dashboard panel. NappAI offers an MCP server with the same tools the assistant uses, so you can work with your account from outside:

From…What you get
Claude Code, with the NappAI pluginBuild, test and fix flows and manage your account from the terminal, with the same instructions the assistant works with.
Claude (the app and cowork) or another MCP clientThe same, by adding NappAI as a connector.
Another application, such as NexusAsk NappAI’s assistant for an automation from that application’s assistant, without opening NappAI.

What it can do and with which permissions

With your API key, an MCP client reaches the same things as the chat assistant: flows, runs, versions, schedules, environments, credentials, the team, alerts, execution profiles, the activity log, billing… See What the assistant can do.

  • It acts as you. It uses the account of whoever created the API key and their role: whatever your role doesn’t allow, the client can’t do either.
  • It asks for permission in the same way. Anything with real effects (running, publishing, scheduling, changing the account) is prepared first without being applied, with the exact change. The client shows it to you and only applies it if you say yes.
  • It is logged. What it does appears in the activity log under your name, marked from an MCP client, and whatever it notes in your memory shows as “noted by an MCP client”.
  • It spends from your account. The runs it launches count towards your usage, like yours.

What you need

  1. A NappAI API key. Create it in Configuration → API Keys, ideally one just for this use, so you can withdraw it without affecting anything else. See API keys.
  2. The address of NappAI’s MCP server. It looks like https://<NappAI server>/flow-editor-mcp/mcp, with the same server you see in a flow’s API Access addresses. If you’re not sure, ask your administrator.

From Claude Code: the NappAI plugin

The plugin brings the instructions NappAI’s assistant works with (planning, searching the catalog, building, fixing, migrating from n8n, Make or Zapier, building a RAG or a voice agent and managing the account) and the commands to connect the MCP server.

1. Install the plugin:

Ventana de terminal
claude plugin marketplace add nappai-dev/nappai-plugin
claude plugin install nappai@napptilus

To have it update itself, in a Claude Code session open /plugin → Marketplaces → napptilus → Enable auto-update.

2. Save your API key in a file only you can read:

Ventana de terminal
mkdir -p ~/.nappai
printf '%s' 'PASTE_YOUR_API_KEY' > ~/.nappai/api-key
chmod 600 ~/.nappai/api-key

3. Connect it. Inside Claude Code:

/nappai:connect https://<NappAI server>/flow-editor-mcp/mcp

It checks the key before saving it and registers the server with a 10-minute timeout, because building or running a large flow can take longer than Claude Code waits by default. Then reopen Claude Code.

CommandWhat it does
/nappai:connect [address]Connects the server with your key. Running it again updates the key, for example after regenerating it.
/nappai:statusTells you whether the plugin is loaded, whether the server is connected and answering, and where the key comes from.
/nappai:disconnectDisconnects the server. It doesn’t delete the key file.

From then on, ask Claude Code what you would ask the assistant: “Build a flow in NappAI that reads the emails with invoices and saves the amounts in my Google sheet”. The plugin’s instructions kick in by themselves when needed.

When it builds a flow, it also leaves the summary note on the canvas. If you don’t want it, tell it.

From Claude (the app and cowork)

In Claude, NappAI is added as a custom connector. When you connect it, you sign in with your NappAI account instead of pasting a key:

  1. In Claude, open Settings → Connectors → Add custom connector.
  2. Give it a name, for example NappAI, and the MCP server’s address: on NappAI in the cloud, https://api.nappai.tech/flow-editor-mcp/mcp.
  3. Open Advanced settings and enter the OAuth Client ID nappai_claude.client. Leave the secret empty.
  4. Click Add and then Connect: NappAI’s sign-in opens. Sign in with your account and you’re back in Claude with the connector ready.

The connector works with your account and your role, just like an API key, and doesn’t need reconnecting as long as you use it at least once a month. If your NappAI is a self-hosted installation, your administrator gives you the address and the client ID, and has to enable sign-in for connectors; if Claude can’t find where to sign in when you connect, that’s what is missing.

The plugin’s instructions also work in Claude if your organization adds it to its library.

Asking for automations from another application

An application connected to NappAI can ask NappAI’s assistant for an automation, as if someone asked for it in the chat. That’s what Nexus does with its Automatizaciones con NappAI (Automations with NappAI) integration: from the Nexus assistant you ask, for example, “when an opportunity is won, create the invoice in Holded”, and NappAI’s assistant plans it, builds it, tests it and leaves it ready for you.

This is how it works:

  1. An administrator of the other application connects it to NappAI with a NappAI API key. It’s best to create it with a NappAI user dedicated to the integration, because the requests are made on behalf of whoever created the key.
  2. From that application you ask for what you want in your own words.
  3. NappAI’s assistant works just as in the chat. What would be buttons in the chat reaches you through the other application: its questions with the options, permission requests and the credentials you need to create in NappAI (with the link to do so). The other application can’t answer or approve anything for you.
  4. When it finishes, it gives you links to the flows it created or changed.

The request is just another assistant conversation: it is saved in the NappAI account and counts towards its usage. For it to work, the assistant must be enabled in the NappAI organization, with its model credential. The Nexus administrator can set up that credential and choose the model without leaving Nexus: NappAI checks the key before saving it. If the assistant isn’t available, the other application receives the reason and how to fix it.