Connect your assistant

One URL, every client:

https://platform.glood.ai/api/v1/mcp

There is no key to paste. The server registers each client dynamically, so nothing you install is a credential. Your first tool call opens a browser: pick which of your organizations that connection may reach, approve, and the client finishes on its own.

Using a client that is not listed below? Any assistant that speaks the Model Context Protocol can connect. See Connect any MCP client.

Pick your client

Install the plugin. It carries the MCP server and the two skills that teach Claude when to use it, so there is nothing else to add:

/plugin marketplace add LoopClub/glood-claude-plugin
/plugin install glood

Or add the server on its own, without the skills:

claude mcp add --transport http glood https://platform.glood.ai/api/v1/mcp

Settings → Connectors → Add custom connector, with the URL above.Nothing to install. claude.ai does not load SKILL.md files, so the server sends the same guidance itself when the connection opens.

Add the server to ~/.codex/config.toml (or .codex/config.toml in a trusted project):

[mcp_servers.glood]
url = "https://platform.glood.ai/api/v1/mcp"

A url instead of a command is what selects the HTTP transport. Then sign in once:

codex mcp login glood

Add the skills too, so Codex knows how to use what it now has:

npx skills add LoopClub/glood-agent-skills

Add the server to ~/.gemini/settings.json:

{
  "mcpServers": {
    "glood": { "httpUrl": "https://platform.glood.ai/api/v1/mcp" }
  }
}

Then add the skills:

npx skills add LoopClub/glood-agent-skills

The Gemini consumer app has no custom connectors and cannot connect. Gemini CLI and Gemini Enterprise can.

Add the server to ~/.config/opencode/opencode.json:

{
  "mcp": {
    "glood": {
      "type": "remote",
      "url": "https://platform.glood.ai/api/v1/mcp",
      "enabled": true
    }
  }
}

Then add the skills:

npx skills add LoopClub/glood-agent-skills

Approving the connection

The first tool call opens your browser at the Glood consent screen.

Tick the organizations this connection may reach

Only what you tick. An organization you leave unticked is invisible to this connection, and the assistant has no tool that can add one.

Approve

The client finishes on its own — nothing to copy back.

Ask it what it can see

“What Glood organizations can you see?”

A good answer names each organization, your role in each, and the stores available to you. Make this the first question in every new conversation.

Custom GPT and Actions

Building a Custom GPT rather than using a ChatGPT connector? Import the OpenAPI description in the GPT builder:

https://platform.glood.ai/api/v1/actions/openapi.json

This is the only path that needs credentials. The GPT builder cannot register itself dynamically, so it needs a client id and secret issued against ChatGPT’s fixed redirect URI. Email support@glood.ai for one rather than trying to register it yourself.

Self-hosted or staging

The URL is the only thing that changes. Point your client at your own API host; discovery, consent and the token exchange all follow from it.

Install the skills

What they teach, and why claude.ai and ChatGPT need nothing installed

Using it

What to ask for, and how to read the answers

AI Assistant

Pick your client

Approving the connection

Custom GPT and Actions

Self-hosted or staging

Next

Install the skills

Using it

​Pick your client

​Approving the connection

​Custom GPT and Actions

​Self-hosted or staging

​Next

Install the skills

Using it

Pick your client

Approving the connection

Custom GPT and Actions

Self-hosted or staging

Next