Connect your agent to ilinxa edge

This is the main path. Claude signs you in with your ilinxa edge account, so you never copy a secret.

1. In Claude, open Settings, then Connectors, then Add custom connector.
2. Paste https://edge.ilinxa.cloud/mcp and save.
3. Choose Connect and sign in to ilinxa edge when asked.
4. Choose where it may act (your account or one project), then the access level: Read only, Editor, or Everything (the full set you can hand to an agent). See Permissions.
5. Approve. Claude can now use your project in any conversation.

claude mcp add --transport http ilinxa https://edge.ilinxa.cloud/mcp

Then run /mcp inside Claude Code, select ilinxa, and sign in. The same project and access-level choices apply.

Any client that supports remote MCP servers over Streamable HTTP can use the same address: https://edge.ilinxa.cloud/mcp. Add it as a remote server in the client's MCP settings and follow its sign-in prompt.

If a client cannot sign in, use a token instead. Signed in to ilinxa edge, use the Connect your agent screen to create a connection and get a token that starts with nbat_. Use it with the local MCP bridge below.

The ilx command manages projects, modules, connections and tokens from a terminal. It ships as @ilinxa/cli.

npx -y @ilinxa/cli --help

npm i -g @ilinxa/cli

ilx auth login            # email and password
ilx auth login --browser  # one-time code; works for Google and GitHub accounts

To point the CLI at a different server, pass --api-url <url> on any command. The hosted service is at https://edge.ilinxa.cloud.

Where your session is stored

The CLI keeps your session in the operating system keychain: Windows Credential Manager, macOS Keychain, or Linux Secret Service. If no usable keychain exists, it stops and offers three options:

• Authenticate with an API token: set ILX_TOKEN (create one with ilx auth token mint <name>).
• Keep the session in a plaintext file (mode 0600): set ILX_USE_FILE_JAR=1.
• Install or unlock an OS keychain.

For clients that only run local commands, @ilinxa/mcp (command ilx-mcp) bridges standard input and output to the remote server. It authenticates with an API token in ILX_TOKEN.

ILX_TOKEN=nbat_your_token_here npx -y @ilinxa/mcp

In a client configuration file:

{
  "mcpServers": {
    "ilinxa": {
      "command": "npx",
      "args": ["-y", "@ilinxa/mcp"],
      "env": { "ILX_TOKEN": "nbat_your_token_here" }
    }
  }
}

Treat the token like a password. You can revoke it at any time.

Every operation is also available over the REST API at https://edge.ilinxa.cloud/api/v1.

To see which operations your connection may call, ask your agent to run the agent.list_operations tool. It returns the catalog of operations available to that connection, and the tools that run an operation take one from that catalog.

Each connection has its own permissions, chosen when you approve it:

• Read only. The agent can look but not change anything.
• Editor. The agent can read, create and publish content. It can move entries to the trash and delete tasks and templates, but cannot empty the trash, change members, modules, backups or permissions, delete or reset databases, or run developer tools.
• Everything. The full set you can hand to an agent, limited to the permissions you hold.

Irreversible actions wait for an owner's approval, and writes are recorded in the audit log. A connection never has more access than you do.

To revoke a connection, open Settings, then Agent connections (account connections), or the project's settings (project connections), and remove it. You can also remove the connector inside Claude. See the privacy policy for what is stored about connections.

These work against a normal project once the matching modules are switched on.

• List my projects and show which modules each one has switched on.
• On the Marketing site in my website project, create a draft blog entry titled "Spring launch", then publish it.
• Show this week's submissions to the Contact form and how many were marked as spam.
• Create a task called "Draft launch post" in my project.

Questions, problems or feedback: edge_support@ilinxa.com. This guide lives at https://edge.ilinxa.cloud/docs.