Guide · Connect your AI

Connect your AI to iERP. Step by step.

To connect your AI to iERP, add the address of the iERP MCP connector as a custom connector in Claude, ChatGPT, Grok, Perplexity, Claude Code, Gemini CLI, Cursor or Ollama, sign in with your iERP account and accept the permissions. From then on your AI works with your own permissions and every call is audited.

Connector address MCP

https://platform.ierp.info/mcp/v1/rpc

It is the same for every assistant and every workspace: you pick the workspace when you authorise.

Protocol: MCP · JSON-RPC 2.0 over HTTP
Authorisation: OAuth 2.1 with PKCE
Permissions: Yours, not one more

01 · Pick your assistant

Your assistant, its exact steps.

These are the same steps the connection wizard in your iERP profile shows you. Pick yours; two minutes and your iERP account are enough.

iEach provider decides on which plans and in which apps it supports custom connectors, and it changes often. If you cannot find the option, check your plan with that provider: the connection wizard in your iERP profile warns you before you start.

Claude

From the mobile app · From the browser

From the mobile app

In a browser (your phone's is fine), open claude.ai/customize/connectors → «Add custom connector».
2
Name: iERP · URL: this address.
url
```
https://platform.ierp.info/mcp/v1/rpc
```
Leave the OAuth client ID and secret empty → tick the trust checkbox → «Add» → sign in to iERP and authorise.
It is already in the Claude app: chat → «+» → Connectors → switch iERP on.

From the browser

Open claude.ai/customize/connectors → «Add custom connector».
2
Name: iERP · URL: this address.
url
```
https://platform.ierp.info/mcp/v1/rpc
```
Leave the OAuth client ID and secret empty → tick the trust checkbox → «Add».
Sign in to iERP and authorise. To use it: chat → «+» → Connectors → switch iERP on.

It stays in your Claude account: mobile, web, desktop and Claude Code.

After connecting

Choose “Always allow” the first time

It will ask permission for one or two iERP tools. With “Always allow” it never asks again; with “allow once”, it asks every time.

Claude Diagram · not a screenshot

Custom connector

NameiERP

URLhttps://platform.ierp.info/mcp/v1/rpc

You sign in to iERP and authorise

iERP · connected

ChatGPT

From the mobile app · From the browser

From the mobile app

In your phone's browser, open chatgpt.com (the app does not run connectors).
Settings → Security and sign-in → turn on «Developer mode».
3
Open the Plugins directory → «+» → Name: iERP · URL: this address · Authentication: OAuth.
url
```
https://platform.ierp.info/mcp/v1/rpc
```
«Analyse tools» → sign in to iERP and authorise → «Create».
Use it on that site: «+» → «Developer mode» → iERP.

From the browser

Open chatgpt.com → Settings → Security and sign-in → turn on «Developer mode».
Open the Plugins directory → «+».
3
Name: iERP · URL: this address · Authentication: OAuth.
url
```
https://platform.ierp.info/mcp/v1/rpc
```
«Analyse tools» → sign in to iERP and authorise → «Create».
To use it: chat → «+» → «Developer mode» → iERP.

It is used from the web: the mobile app does not run custom connectors.

After connecting

Choose “Always allow” the first time

It will ask permission for one or two iERP tools. With “Always allow” it never asks again; with “allow once”, it asks every time.

ChatGPT Diagram · not a screenshot

Custom connector

NameiERP

URLhttps://platform.ierp.info/mcp/v1/rpc

You sign in to iERP and authorise

iERP · connected

Gemini

From the mobile app · From the browser

In Spain the Gemini app does not support connectors: it only exists in the United States and no plan unlocks it.

With a computer, Gemini CLI does connect, and for free. On your phone, Claude or Grok work.

In Spain the Gemini web app does not support connectors: it only exists in the United States and no plan unlocks it.

What does work, and for free, is Gemini CLI.

See the Gemini CLI steps →

Gemini Diagram · not a screenshot

Gemini app and web
No connectors in Spain

Gemini CLI
Connects over MCP

Grok

From the mobile app · From the browser

From the mobile app

In a browser (your phone's is fine), open grok.com/connectors.
«New Connector» → «Custom».
3
Name: iERP · URL: this address → sign in to iERP and authorise.
url
```
https://platform.ierp.info/mcp/v1/rpc
```
In the Grok app: new chat → tools → switch iERP on. If it shows «connected» but with no tools, your plan does not include authentication.

From the browser

Open grok.com/connectors → «New Connector» → «Custom».
2
Name: iERP · URL: this address.
url
```
https://platform.ierp.info/mcp/v1/rpc
```
Sign in to iERP and authorise. If nothing opens and it shows «connected» but with no tools, your plan does not include authentication.
To use it: new chat → tools → switch iERP on.

After connecting

Grok will not ask you anything

Grok does not ask permission tool by tool: it uses every tool you allow. If that does not suit you, authorise iERP read-only.

Grok Diagram · not a screenshot

Custom connector

NameiERP

URLhttps://platform.ierp.info/mcp/v1/rpc

You sign in to iERP and authorise

iERP · connected

Perplexity

From the mobile app · From the browser

From the mobile app

In a browser (your phone's is fine), open perplexity.ai → Account settings → Connectors.
«+ Custom connector» → «Remote».
3
Name: iERP · URL: this address · Transport: «Streamable HTTP» · Authentication: OAuth → tick the risk checkbox → «Add».
url
```
https://platform.ierp.info/mcp/v1/rpc
```
Press the connector → sign in to iERP and authorise. It is already in the app.

From the browser

Open perplexity.ai → Account settings → Connectors.
«+ Custom connector» → «Remote».
3
Name: iERP · URL: this address · Transport: «Streamable HTTP» · Authentication: OAuth → tick the risk checkbox → «Add».
url
```
https://platform.ierp.info/mcp/v1/rpc
```
Press the connector → sign in to iERP and authorise.

It stays in your Perplexity account, in the app too.

After connecting

Choose “Always allow” the first time

It will ask permission for one or two iERP tools. With “Always allow” it never asks again; with “allow once”, it asks every time.

Perplexity Diagram · not a screenshot

Custom connector

NameiERP

URLhttps://platform.ierp.info/mcp/v1/rpc

You sign in to iERP and authorise

iERP · connected

Claude Desktop

On your computer

Install Claude Desktop from claude.ai/download → Settings → Connectors → «Add custom connector».
2
Name: iERP · URL: this address.
url
```
https://platform.ierp.info/mcp/v1/rpc
```
Leave the OAuth client ID and secret empty → tick the trust checkbox → «Add».
Sign in to iERP and authorise.

It stays in your Claude account: mobile, web, desktop and Claude Code.

After connecting

Choose “Always allow” the first time

It will ask permission for one or two iERP tools. With “Always allow” it never asks again; with “allow once”, it asks every time.

Claude Desktop Diagram · not a screenshot

Custom connector

NameiERP

URLhttps://platform.ierp.info/mcp/v1/rpc

You sign in to iERP and authorise

iERP · connected

Claude Code

On your computer

1
Paste this into a terminal (with «--scope user» you get it in every project).
bash
```
claude mcp add --transport http ierp https://platform.ierp.info/mcp/v1/rpc
```
«claude» → «/mcp» → iERP → «Authenticate» → authorise in the browser.
Done. If you already have it on claude.ai with this account, it shows up on its own.

After connecting

Choose “Always allow” the first time

Tell it “always allow the ierp tools” (or add mcp__ierp__* to your permissions) and it will stop asking.

Claude Code Diagram · not a screenshot

$ claude mcp add --transport http ierp https://platform.ierp.info/mcp/v1/rpc

the browser opens: you authorise in iERP

iERP · connected

Gemini CLI

On your computer

Install github.com/google-gemini/gemini-cli and paste this into a terminal.

bash

gemini mcp add --transport http --scope user ierp https://platform.ierp.info/mcp/v1/rpc

«gemini» → «/mcp auth ierp» → sign in to iERP and authorise.
Check with «/mcp» that iERP shows as connected.

Gemini CLI Diagram · not a screenshot

$ gemini mcp add --transport http --scope user ierp https://platform.ierp.info/mcp/v1/rpc

the browser opens: you authorise in iERP

iERP · connected

Cursor

On your computer

Open (or create) ~/.cursor/mcp.json.

Paste this and save. «type» must be «http»: with «streamable-http» Cursor fails silently.

json

{
  "mcpServers": {
    "ierp": {
      "type": "http",
      "url": "https://platform.ierp.info/mcp/v1/rpc"
    }
  }
}

Restart Cursor → Customise → MCPs: iERP shows «Needs authentication».
«Connect» → sign in to iERP and authorise.

Doesn't your version of Cursor ask you to sign in? See how to do it with a personal token

Cursor Diagram · not a screenshot

~/.cursor/mcp.json

{
  "mcpServers": {
    "ierp": {
      "type": "http",
      "url": "https://platform.ierp.info/mcp/v1/rpc"
    }
  }
}

iERP · connected

Ollama

On your computer

Install ollama.com/download and pull a model that can use tools (7B or bigger): «ollama pull qwen2.5:7b-instruct-q4_K_M».
The Ollama app does not speak MCP yet; use ollmcp: «pip install mcp-client-for-ollama» (or «uvx mcp-client-for-ollama»).
In iERP, open My profile → Connect your AI → «Advanced options» and issue a token of type «API key» with ONLY the scope you will use (e.g. crm.read). Copy it: it is shown once.

Save this as «ierp-mcp.json» and replace TOKEN with the one you just copied.

json

{
  "mcpServers": {
    "ierp": {
      "type": "streamable_http",
      "url": "https://platform.ierp.info/mcp/v1/rpc",
      "headers": {
        "Authorization": "Bearer TOKEN"
      }
    }
  }
}

Start it: «ollmcp --servers-json ierp-mcp.json --model qwen2.5:7b-instruct-q4_K_M».

After connecting

It will ask you to confirm tool by tool

ollmcp asks «y» or «n» before each tool: that is normal. If it answers without reaching iERP, issue a token with fewer permissions or use a bigger model.

Ollama Diagram · not a screenshot

ierp-mcp.json

{
  "mcpServers": {
    "ierp": {
      "type": "streamable_http",
      "url": "https://platform.ierp.info/mcp/v1/rpc",
      "headers": {
        "Authorization": "Bearer TOKEN"
      }
    }
  }
}

iERP · connected

02 · What happens when you connect

Five OAuth steps. No password travels.

Your assistant never gets your password or a key to paste: iERP grants it a permission in your name, for the workspace you choose, and you can take it back whenever you like.

01
Your AI asks for access

It calls the connector without credentials and iERP tells it where to authorise. Your assistant registers itself and prepares a PKCE challenge: there is no client ID or secret to copy.
02
You sign in to iERP

The usual iERP sign-in screen opens: with your password, your passkey or your two-factor code, if you have them turned on.
03
You see and accept the permissions

You pick the workspace and see exactly what it will be able to read. The changes checkbox comes ticked: untick it, or keep only some modules, if you would rather it only read.
04
Your AI gets its token

A single-use code is exchanged for a one-hour token that renews itself while you use it, bound to the connector address. If it goes unused for 30 days, it expires.
05
You revoke it whenever you like

In My profile → Connect your AI you see each connection with its latest activity. Revoking it cuts access instantly, renewal included.

Calls the connector without a token POST /mcp/v1/rpc
401 · where to authorise WWW-Authenticate · resource_metadata
Registers and sends the PKCE challenge /oauth/register · code_challenge S256
Opens the authorisation for you /oauth/authorize
You sign in
Permissions: workspace, read, changes
Authorise
Single-use code redirect_uri?code=…
Exchanges the code: 1 h token + renewal POST /oauth/token
Calls with your token Authorization: Bearer …
Revoke, from your profile

03 · Inside the MCP

850 actions. Six tools in sight.

MCP (Model Context Protocol) is the open standard an AI assistant uses to discover and use external tools. iERP publishes its tools on a single MCP server, which your assistant talks to in JSON-RPC.

AI apps ask for permission tool by tool, and with hundreds of them that would be hundreds of prompts. So a connection authorised from your app sees the catalogue in compact mode: it searches for the action it needs and runs it by name. It asks for permission once or twice, not every time.

iERP catalogue 850 actions across seven modules

What your app sees · 6 tools

sistema.buscar_herramientas searches the catalogue for what this connection can do
sistema.ejecutar runs one of them, with its arguments
sistema.ejecutar_lote repeats the same one, up to 25 times
system.ping checks the connector answers
system.pendingList pending proposals and their result
system.pendingResult pending proposals and their result

JSON-RPCA query and a task, end to end

→ Searches for the action

{"jsonrpc": "2.0", "id": 7, "method": "tools/call",
 "params": {"name": "sistema.buscar_herramientas",
  "arguments": {"consulta": "tickets about to breach their SLA", "limite": 3}}}

← Finds one, read-only · result.content[0].text

{"total": 1, "herramientas": [
  {"herramienta": "soporte.tickets_sla_riesgo",
   "readOnly": true, "inputSchema": {…}}]}

→ Runs it

{"jsonrpc": "2.0", "id": 8, "method": "tools/call",
 "params": {"name": "sistema.ejecutar",
  "arguments": {"herramienta": "soporte.tickets_sla_riesgo",
                "argumentos": {"filtro": "riesgo"}}}}

← Response

{"items": [{"cliente": "Lera Architects", "prioridad": "alta",
            "sla_label": "due in 3 h"}],
 "count": 1, "filtro": "riesgo"}

→ Creates a task with an anti-duplicate key

{"name": "sistema.ejecutar", "arguments": {
  "herramienta": "proyectos.create_tarea",
  "argumentos": {"nombre": "Call Lera about the urgent ticket", "proyecto_id": 312,
                 "_idempotencia": "4f9c1e2a-7d3b-4c8e-9a10-2b6f5d8e1c37"}}}

← If it drops and retries, nothing is duplicated

{"repetida": true, "status": "created", "id": 4182}

Sample data

850+ Published actions

6 Tools in compact mode

25 Calls per batch, at most

240 Requests per minute per connection

_idempotencia
A retry duplicates nothing

Every tool that writes accepts an «_idempotencia» argument with a key your AI chooses. If the connection drops and repeats the call with the same key within 24 hours, iERP does not run it again: it returns the first result, flagged «repetida».
mcp.rafaga_destructiva
A burst of deletions stops itself

iERP counts the removals each connection chains together. Past the threshold, ten in five minutes by default, it stops running them and explains why; once the window passes, it reopens on its own.
sistema.ejecutar_lote
Many calls, one turn

«sistema.ejecutar_lote» repeats the same action up to 25 times with a list of arguments: approving the week's hours or reassigning tasks. It is not atomic, and it does not accept actions that delete, void or archive.
confirmacion_ierp
Bulk actions need a second call

Emailing a whole list or invoicing a period does not run on the first call: iERP returns a code tied to those exact arguments and your AI has to repeat the call with it, telling you first.

04 · Permissions and security

With your permissions. With your name on every call.

What your AI can do comes from what you can do in iERP, and it is checked on every request. This is what the connector does, and also what it does not.

01
It inherits your permissions, live

The connection's permissions come from yours: your assistant never asks for them. If a module is taken away from you tomorrow, your AI loses it on the next request; if you get a new one, it does not gain it until you authorise again.
02
Writing is flagged

Every tool reaches your app flagged as read-only, write or destructive, so the app asks you to confirm. iERP does not ask you about each change: it runs the ones you authorised when connecting.
03
Every call, audited

It records which tool your AI asked for, when and with what data, with the request and an excerpt of the response encrypted with your workspace key. And we let you know about every change it makes.
04
What cannot be done from outside

Your AI can draft an automation flow, but not switch it on. With self-service permissions it only acts on you, and jobs that sweep the whole installation are not offered to any external connection.
05
You revoke instantly

Each connection is a card in My profile → Connect your AI, with its app, its permissions and its last use. Revoke it and its token and its renewal stop working on the spot.
06
No keys floating around

With OAuth your assistant never sees your password, and iERP only stores a hash of each token: the full value of a personal token is shown only once.

My profileActive connections

Claude AI connection (OAuth) · last used 2 min ago Read and changes
ChatGPT AI connection (OAuth) · last used yesterday Read only
Reports script AI connection (MCP) · expires in 82 days Read only

Sample data

05 · Your own agents and scripts

Your agents, with a personal token.

For a script, your own agent or an MCP client without sign-in, issue a personal token and send it in the Authorization header. Same connector, same rules.

Where to create it

In iERP, My profile → Connect your AI → «Advanced options», type «AI connection (MCP)». Or, in the connection wizard, «Another tool», which issues it in one click.
Which permissions it carries

Yours, trimmed to reading: unless you ask, it comes out read-only. If you tick the changes checkbox, it adds your write permissions; in the form it comes ticked, so untick it if you only want to read.
How long it lasts

90 days. It is shown once: copy it when you issue it. When it expires, or if you lose it, revoke it and issue another.
Which catalogue it sees

The token from the form sees the full catalogue of what you can do, without compact mode; the one from «Another tool» is compact, designed for apps that ask for permission per tool.

Keep it like a password: whoever has it can do everything the token allows. If it leaks, revoke it from your profile.

bash · With curl

# Which tools you have

curl -s https://platform.ierp.info/mcp/v1/rpc \
  -H "Authorization: Bearer $IERP_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

{"jsonrpc":"2.0","id":1,"result":{"tools":[{"name":"soporte.tickets_sla_riesgo", "annotations":{"readOnlyHint":true}, …}, …]}}

# Calling one

curl -s https://platform.ierp.info/mcp/v1/rpc \
  -H "Authorization: Bearer $IERP_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"soporte.tickets_sla_riesgo",
                 "arguments":{"filtro":"riesgo"}}}'

{"jsonrpc":"2.0","id":2,"result":{"isError":false,"content":[{"type":"text","text":"{\"items\":[…],\"count\":1}"}]}}

Sample data

json · With an MCP client

{
  "mcpServers": {
    "ierp": {
      "type": "streamable_http",
      "url": "https://platform.ierp.info/mcp/v1/rpc",
      "headers": {
        "Authorization": "Bearer TOKEN"
      }
    }
  }
}

In your client's MCP configuration, replace TOKEN with yours. It is the same format ollmcp uses.

06 · Troubleshooting

If something is off, it is almost always one of these.

First of all, check

The address ends in /mcp/v1/rpc
You signed in to iERP and pressed «Authorise»
Your app and your plan support custom connectors
You chose «Always allow» the first time

«Permitir siempre»
My AI asks for permission every time it queries iERP

The first time, your app asks for permission for one or two iERP tools. Choose «Always allow» and it will not ask again; with «allow once», it asks every time. In Claude Code, say «always allow the ierp tools».
tools: []
It says «connected», but with no tools

It happens in Grok when authentication does not complete: your plan with that provider does not include it. Check your plan, or connect another assistant with the same address.
chatgpt.com · Developer mode
My app does not show the option to add a connector

Each provider decides on which plans and in which apps there are custom connectors. ChatGPT runs them from the web, with developer mode on, not from the mobile app. In Claude, Grok and Perplexity you add them on the web and they then show up in the app.
"type": "http"
Cursor never shows iERP

Check that the «type» in ~/.cursor/mcp.json is «http»: with «streamable-http», Cursor fails without a word. If your version does not ask you to sign in, connect it with a personal token.
sin_permiso · mcp.forbidden
My AI says it is not allowed to do something

Your AI cannot do more than you. When it looks for an action that exists but you cannot use, iERP tells it which permission is missing. Ask whoever manages your workspace; your connection will have it on the next request.
HTTP 401
The connection stopped working

An OAuth connection renews itself while you use it and expires after 30 days unused; a personal token, after 90 days. If you revoked it or it expired, connect again: your app will take you back to iERP to authorise.
mcp.rafaga_destructiva
My AI says it has chained too many removals

That is the burst brake: iERP cuts a connection's series of deletions or voids past the threshold. Wait a few minutes, or do that clean-up from the screen, where it is still one click away.
qwen2.5:7b-instruct
With Ollama, the model answers without querying iERP

A small model gets lost among many tools. Use one of 7B or more and a token with only the scope you will use; ollmcp asks «y» or «n» before each tool, and that is normal.

Questions about connecting your AI

How do I connect Claude to my ERP?

Open claude.ai/customize/connectors, add a custom connector named iERP with the connector address, leave the OAuth ID and secret empty, sign in to iERP and authorise. It stays in your Claude account: mobile, web, desktop and Claude Code.

What is the address of the iERP MCP server?

The one shown at the top of this page, ending in /mcp/v1/rpc. It is the same for any assistant and any workspace: you pick the workspace when you authorise.

Do I need an API key to connect ChatGPT or Claude?

No. Claude, ChatGPT, Grok, Perplexity, Claude Code, Gemini CLI and Cursor authorise with OAuth: you sign in with your iERP account and accept the permissions. A personal token is only needed for your own scripts, for agents without sign-in and for Ollama.

How do I disconnect my AI from iERP?

In iERP, open My profile → Connect your AI and press «Revoke» on that connection's card. Your assistant loses access instantly; if you want it back, connect it again with the same address.

Why can't my AI find an iERP action?

Because it only sees the actions you can use in that workspace, from the modules it subscribes to. If the action exists and you lack the permission, iERP tells your AI which permission is missing.

Can I use iERP with a local model, such as Ollama?

Yes. The Ollama app does not speak MCP yet, but the ollmcp client does: you issue a personal token with the scope you will use, put it in its configuration and use a tool-capable model of 7B or more.

Your AI already talks. Now, with your company.

Create your account and connect your assistant in two minutes, or book a demo and we will connect it with you.

Create my account Book a demo

Why a headless ERP →

Connect your AI to iERP. Step by step.

Your assistant, its exact steps.

From the mobile app

From the browser

From the mobile app

From the browser

From the mobile app

From the browser

From the mobile app

From the browser

Five OAuth steps. No password travels.

Your AI asks for access

You sign in to iERP

You see and accept the permissions

Your AI gets its token

You revoke it whenever you like

850 actions. Six tools in sight.

A retry duplicates nothing

A burst of deletions stops itself

Many calls, one turn

Bulk actions need a second call

With your permissions. With your name on every call.

It inherits your permissions, live

Writing is flagged

Every call, audited

What cannot be done from outside

You revoke instantly

No keys floating around

Your agents, with a personal token.

Where to create it

Which permissions it carries

How long it lasts

Which catalogue it sees

If something is off, it is almost always one of these.

My AI asks for permission every time it queries iERP

It says «connected», but with no tools

My app does not show the option to add a connector

Cursor never shows iERP

My AI says it is not allowed to do something

The connection stopped working

My AI says it has chained too many removals

With Ollama, the model answers without querying iERP

Questions about connecting your AI

Your AI already talks. Now, with your company.