Bring your own AI

Connect Skuvelo to your AI

Point your own ChatGPT, Claude, Grok, or other MCP-compatible AI assistant at Skuvelo, so it can answer questions about your inventory, planning, suppliers, and purchasing. Read access only, permissioned to your own role, revocable in one click.

What this is

Skuvelo doesn't run or fund your AI. You bring your own subscription, and Skuvelo exposes a narrow set of business tools it can call: inventory levels, replenishment planning, suppliers, purchasing, and setup diagnostics. A connection only ever asks for read access today; there is nothing to approve for making changes yet. No request from your AI can see more than your own Skuvelo role already lets you see.

The connection uses the Model Context Protocol (MCP), an open standard most modern AI assistants already support. You approve it once, on Skuvelo's own sign-in screen, never inside the AI client, and you can end it at any time from Skuvelo.

The connector endpoint

Every client connects the same way: give it this address as a custom connector or MCP server. The client handles the rest: discovering how to sign in, and opening your browser to Skuvelo's own consent screen.

https://api.skuvelo.com/mcp

Connect from your client

Client menus change more often than this page does, so these are deliberately short. Look for "connectors" or "MCP servers" in your AI client's settings if a step has moved.

ChatGPT

  1. In ChatGPT, open Settings › Connectors › Add custom connector.
  2. Paste the connector endpoint below.
  3. ChatGPT sends you to Skuvelo to sign in (if needed) and approve the connection. The AI never sees your Skuvelo password.

Claude

  1. At claude.ai, open Settings › Connectors › Add custom connector.
  2. Paste the connector endpoint below.
  3. Claude sends you to Skuvelo to sign in (if needed) and approve the connection.

Grok

  1. In Grok, add a custom connector (MCP server).
  2. Paste the connector endpoint below.
  3. Grok sends you to Skuvelo to sign in (if needed) and approve the connection.

Other MCP client

  1. Any client that speaks the Model Context Protocol can connect the same way: add Skuvelo as an MCP server using the connector endpoint below.
  2. The client discovers Skuvelo's OAuth details automatically and opens your browser to sign in and approve the connection. No API key to copy and paste.

What permissions mean

When you approve a connection, you're shown exactly what it can do in plain language, for example "View inventory & planning" or "View suppliers & purchasing", never an internal code. Two things narrow what it can actually see:

  • The permissions you approved. A connection only ever asks for read access today; there is nothing to approve for making changes yet.
  • Your own Skuvelo role. The connection can never see more than you can see in Skuvelo yourself. If your role can't view purchasing, neither can your AI, no matter what it was granted.

How to disconnect

Go to Connect your AI in Skuvelo and select Disconnect next to the assistant you want to remove. Access ends immediately. The next request from that client is refused, not just hidden. Removing the connector inside the AI client's own settings stops that client from calling Skuvelo, but only Disconnect in Skuvelo revokes the grant itself. Use Disconnect here when you want access ended for good.

Access follows you, and only you

An AI connection is tied to your own membership, not a shared credential. If your role changes or your access to Skuvelo is removed, the connection loses access on its very next request, and you can revoke it yourself, instantly, at any time from Connect your AI in Skuvelo.