Connect your AI assistant

Config snippets for Claude Desktop, Claude Code, Cursor, ChatGPT, Gemini CLI and every other MCP client.

You need exactly two things: an address and a key. Nothing to install, no extension to download, nothing to update later on.

Don't type it by hand

Every page that shows a key comes with a Connect guide card whose snippets already have your key in them, so all you do is press copy. What follows explains those snippets, for anyone who wants to understand what they are pasting.

Where to get the address and the key

You are	Go to	Address
A member (any role)	My access	the business hub
A manager issuing keys to other people	Member keys	the business hub
A machine integration	server → Keys tab	that one server's own address
A manager who wants an AI to administer for them	Admin MCP	the management endpoint

A hub address looks like https://<your company domain>/api/mcp/biz/<business id>. The business id is a fixed 12-character string; you can read it under Business settings.

Claude Desktop

Open Settings → Developer → Edit Config, paste into claude_desktop_config.json, then restart Claude.

{
  "mcpServers": {
    "cong-ty-abc": {
      "type": "http",
      "url": "https://coreskill.congty.com/api/mcp/biz/a3f1c9d2b7e4",
      "headers": {
        "Authorization": "Bearer cek_1a2b3c4d_..."
      }
    }
  }
}

The entry name (cong-ty-abc) is generated by CoreSkill from the business name or the server name, with accents stripped. Rename it however you like. It is only a display label inside Claude.

If the file already has an mcpServers block, add one entry inside it; don't paste over the whole file, because that wipes out every other MCP connection you have.

Claude Code

Run this once in your terminal:

claude mcp add --transport http cong-ty-abc \
  https://coreskill.congty.com/api/mcp/biz/a3f1c9d2b7e4 \
  --header "Authorization: Bearer cek_1a2b3c4d_..."

Cursor

Save it as .cursor/mcp.json in your project, or add it under Cursor Settings → MCP. The content is identical to Claude Desktop.

ChatGPT

Open ChatGPT Settings → Connectors.
Choose "Add MCP server".
Paste your hub address into Server URL.
Add a Header: Authorization: Bearer <your key>.

If the build of ChatGPT you have can't set headers, the Connect guide card carries a Key in the URL option, which is the address with the key tacked onto the end. Read the warning next to it before you use it.

Gemini CLI

Add it to ~/.gemini/settings.json. Note that the field is called httpUrl here, unlike Claude:

{
  "mcpServers": {
    "cong-ty-abc": {
      "httpUrl": "https://coreskill.congty.com/api/mcp/biz/a3f1c9d2b7e4",
      "headers": {
        "Authorization": "Bearer cek_1a2b3c4d_..."
      }
    }
  }
}

Other clients

The JSON tab holds a generic config that works with most clients that take a JSON server entry:

{
  "mcpServers": {
    "cong-ty-abc": {
      "url": "https://coreskill.congty.com/api/mcp/biz/a3f1c9d2b7e4",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer cek_1a2b3c4d_..."
      }
    }
  }
}

Check that it works

Restart your AI assistant after editing the config file.
Ask it: "list the skills you have".
It will call list_skills and read the list back. Nothing there may simply mean no server has been shared with you yet. Check the My access page.
Open Usage logs in CoreSkill to confirm.
That call has to show up with your name, the tool name and status OK. This is the surest way to know the connection is live.

How the AI uses skills

Your assistant has three read-only tools. You never call them by hand, because it picks them itself when the work looks related:

list_skills: Lists every skill you can read, with the server it lives in. The AI calls this one first.
get_skill: Fetches the full text of one skill by name, plus the list of its attached files.
get_skill_file: Fetches the contents of one attached file.

When the same skill name exists on several servers, the AI is told to call again with the server name. If that keeps happening, rename the skills so they differ. That is easier on people and machines alike.

There are no write tools

Both the hub and a server expose only the three read tools above. A member's AI assistant cannot edit, delete or create anything in CoreSkill. For an AI that does administrative work you need an Admin MCP key, which is a system of its own.

When it won't connect

Symptom	Usual cause
The client says it can't authenticate	Wrong key, a stray space picked up while copying, or a missing `Bearer` in front of the key
It connects but shows no skills	No server has been shared with you yet. See My access
It ran fine and then suddenly broke	The key was revoked or expired, or your membership was suspended
An odd client error, and nothing in the log	Wrong address, or a key from another system pasted in (`csk_` into the hub, say)
The whole company is down at once	The business is suspended, or an operator turned off the master switch

The log records denied calls too, so if you see a Denied row with your key on it, the key did reach the server, so the problem is the key and not the address.