Skip to content
Loupine

Connector documentation

How to connect your company's Loupine library to Claude and ChatGPT, what each tool does, and what to ask for once it is connected.

Last updated 2026-08-10

What the connector does

Loupine is your company's shared library of prompts and skills. The connector puts that library inside the AI assistant your team already uses: the assistant can search the library, load the full text of an approved prompt or skill before doing the work, and save a good result back as a new team asset — without anyone leaving the chat.

It is one remote MCP server over streamable HTTP. There is nothing to install on anyone's machine.

https://web.loupine.app/mcp

Before you connect

  • Your company needs a provisioned Loupine organization. There is no self-service sign-up: organizations are created by us when a pilot or contract starts. Write to hello@loupine.app to start one.
  • You sign in with your company's existing single sign-on. You will not create a password.
  • If your assistant is a company workspace (ChatGPT Business/Enterprise, Claude Team/Enterprise), a workspace admin usually has to add the connector once for everyone.

If sign-in ends with "Organization not provisioned", your identity is fine but your company does not have a library yet — that is the message to forward to us.

Connect it in Claude

  1. 1Open Settings, then Connectors.
  2. 2Choose to add a custom connector.
  3. 3Paste the connector URL: https://web.loupine.app/mcp
  4. 4Confirm, then click Connect and sign in with your company account.
  5. 5Ask Claude what is in your library to confirm the tools answer.

Connect it in ChatGPT

  1. 1Open Settings, then Connectors.
  2. 2Add a connector using an MCP server URL.
  3. 3Paste the connector URL: https://web.loupine.app/mcp
  4. 4Sign in with your company account when prompted.
  5. 5In a new chat, enable the connector and ask it to search your library.

ChatGPT also expects tools literally named search and fetch. The connector exposes both as thin aliases over the same library and the same access rules, so deep research works without any extra setup.

What each tool does

search_library — read only
Searches your personal assets, your teams' assets, and the built-in system library by keyword over name, tags, description and body. Returns summaries without the instruction text.
use_asset — read only
Returns the full current instructions for one prompt or skill, by id or slug. This is the only tool that returns instruction text, and it always returns the latest version.
list_teams — read only
Lists the libraries you can publish to: your personal library plus every team you belong to.
save_asset — writes
Publishes a prompt or skill to your personal library or to a team. Saving over an existing asset creates a new version; history is kept and readers get the latest.
search / fetch — read only
The OpenAI-shaped aliases over search_library and use_asset. Same content, same access rules.

Organization admins and team owners also see the management tools: list_org_members, manage_membership, invite_to_team, manage_team and set_org_role. Everyone else never sees them.

Read-only tools are annotated as such, so your assistant can run them without interrupting you. Every tool that writes is annotated as a write and asks you first.

Things to ask once it is connected

  • "Prep me for tomorrow's discovery call with Meridian — check our library for how we do these first." (searches, then loads the team's skill)
  • "Which libraries can I publish to?" (lists your personal library and your teams)
  • "Load our post-demo follow-up skill and rewrite this draft so it matches." (loads the full instructions, then applies them)
  • "That worked — save it to the Sales team as 'Renewal outreach', tagged renewals." (publishes a new team asset)
  • "Add carla@acme.com to the Sales team as an owner." (admins and team owners only)

Who sees what

  • Everyone sees their personal library, the libraries of the teams they belong to, and the built-in system library.
  • The system library is read-only. Saving over it is refused; save a copy to your own library or a team instead.
  • Team owners manage the teams they own. Organization admins manage every team.
  • Nothing crosses organizations. A request is scoped to one organization on the server, whatever the assistant asks for.

When something looks wrong

Search finds nothing
Matching is keyword-based. Try the words a colleague would have put in the title, or ask for the whole library with an empty search.
"This asset is no longer available"
The asset was archived, or it belongs to a library you are not a member of. Ask an admin to add you to the team.
The tools answer "unavailable"
The connector is up but could not resolve your account or the service is degraded. The message says which; forward it to hello@loupine.app.
You cannot save to a team
You are not a member of it. Call list_teams — or just ask "which libraries can I publish to?" — to see your options.

Data and support

The connector returns library content into the assistant that asked for it, and only content the signed-in user is entitled to read. What we store, who processes it, and how long we keep it is set out in the privacy policy at loupine.app/en/privacy.

Support, security reports, and organization requests: hello@loupine.app. We reply within one business day.