Connecting an AI Assistant

How to connect Claude or another MCP client to your Skyline organisation, and how to disconnect it again

This page is the step-by-step guide to connecting an assistant. For what an assistant is and what it can never do, see AI Assistant (MCP).

Before you start

An organisation admin has to switch on AI access first, at Settings → AI access. Nothing can connect until that is on.
An assistant acts for your whole organisation, not just for the person who connected it. Only connect one you are happy to have reading your organisation's data.

The connection details

Your assistant needs one address:

https://customer-mcp.skylinedigital.xyz/mcp

That is the only address to use. Skyline will never ask you for a password or an API key inside a chat — signing in always happens on a Skyline page in your browser.

Connecting from Claude

On claude.ai, add Skyline as a custom connector and paste the address above. Claude sends you to Skyline to sign in and approve the connection, and then you are done.

In Claude Code, add it from the command line:

claude mcp add --transport http skyline https://customer-mcp.skylinedigital.xyz/mcp

Connecting from Codex

codex mcp add skyline --url https://customer-mcp.skylinedigital.xyz/mcp

Connecting from another MCP client

Use the same address. Most clients take a small configuration block like this one:

{
  "mcpServers": {
    "skyline": {
      "type": "http",
      "url": "https://customer-mcp.skylinedigital.xyz/mcp"
    }
  }
}

The client works out the sign-in flow for itself — you do not need to enter anything else. Clients that run on your own machine, such as desktop or command-line apps, complete the sign-in against your local machine, which is the normal pattern for those clients.

Hosted web clients other than Claude are not accepted today, and signing in always happens on a Skyline page in your browser.

What the approval screen shows

The screen tells you which assistant is asking, and which organisation it will act for. Approving records that consent against your organisation.

Before you approve, check both: that the name shown is the assistant you actually started, and that the organisation is the right one.

Turning one assistant off, or all of them

Revoking a connection disconnects that one assistant. It is refused the next time it tries to do anything, and it cannot renew itself.

Whoever connected it can connect it again while AI access is still on for your organisation, and each reconnection is recorded as a new connection. So switching AI access off is the organisation-wide stop.

Skyline can also disable AI access for your organisation from its side. When that happens, the reason is shown to you in the portal.

If something is not working

"AI assistant access is temporarily unavailable. Please try again later." — nothing is wrong with your setup. Try again shortly.
"This action is temporarily unavailable. Please try again later." — that one tool is paused. The rest still work.
"AI assistant access for this organisation is currently disabled. Please contact Skyline support." — access has been switched off for your organisation. Contact support.
"AI assistant access could not be verified right now. Please try again shortly." — a temporary check failed. Try again shortly.
The assistant says it has been signed out, or asks you to reconnect — the connection was revoked or has expired. Connect it again, as long as AI access is still on.
The assistant refuses to pay an IBAN or wallet address you typed into the chat — that is expected. It can only pay counterparties you have already created and verified in Skyline.

For developers

Sign-in is standard OAuth 2.1 with dynamic client registration. There are no API keys, ever — a client registers itself and then completes an ordinary browser sign-in against Skyline.

Discovery is served from the same host:

https://customer-mcp.skylinedigital.xyz/.well-known/oauth-protected-resource — protected-resource metadata, also served at /.well-known/oauth-protected-resource/mcp.
https://customer-mcp.skylinedigital.xyz/.well-known/oauth-authorization-server/oauth — authorization-server metadata.

Tools and their schemas are self-describing over MCP, so there is no separate API reference to read.