Admin MCP

Let your own AI assistant create servers, upload skills, invite people and issue keys, all from inside the chat window.

This is the write side of CoreSkill, kept entirely apart from the read side your staff use. You hand your own AI assistant a cmk_ key, then ask it to do admin work in plain language: *"create a Marketing server and upload these three skill files"*.

Owners and admins only

A manager or a member who opens this page gets Page not found. The key is pinned to exactly one business and can never reach across to another one.

Create a key

Go to Admin MCP → click New agent key.
Set the Key name to the app that will hold it, for example Claude Desktop.
Tick the Permissions you want to grant, then click Create.
Read and Write are ticked for you, Delete is not. Leave it that way unless you truly need it.
Copy the key now. It is shown only once.

Each business can hold 10 active keys. This kind of key takes no expiry date, so you either revoke it or delete it.

The permission matrix

Area	Read	Write	Delete
Servers	list servers	create, rename, re-scope, change visibility	delete a server for good
Skills & files	read skills and files	create, edit, upload a package, write files	delete skills and files
Employee keys	list keys	issue keys, revoke keys	none
Members & departments	see departments, see people	invite people	none

Think hard before you grant Delete

Delete lets the AI wipe out servers, skills and files. One vague sentence from you can be read as an order to delete. The delete tools force the AI to send an explicit confirmation, but the best guard is still not granting the permission in the first place.

There is deliberately no delete for keys and members: a key can only be revoked through the AI (a hard delete would destroy the trail you reconcile against), and taking someone out of the business is a job a person does by hand in the interface.

What the AI can do

Servers: list_skill_servers, create_skill_server, rename_skill_server, set_server_visibility, set_server_scope, delete_skill_server
Skills: list_skills, get_skill, create_skill, update_skill, upload_skill_archive, delete_skill
Attached files: list_skill_files, get_skill_file, put_skill_file, delete_skill_file
Keys: list_keys, create_key (service key), create_member_key (member key), revoke_key
People: list_departments, list_members, invite_member

Connecting

The address is https://<your company domain>/api/mcp/agent. The Connect your AI card in the right-hand column already holds a snippet for each app. It works exactly like the Connect your AI assistant section, only the address and the key differ.

{
  "mcpServers": {
    "coreskill-manager": {
      "type": "http",
      "url": "https://coreskill.congty.com/api/mcp/agent",
      "headers": {
        "Authorization": "Bearer cmk_1a2b3c4d_..."
      }
    }
  }
}

Getting good results

Tell the AI to list before it edits: *"list my skill servers"*. It needs the real ids, not a guess.
To change a skill, have it read the current version first: *"read the bao-cao-tuan skill, then add a section on the quarterly figures"*. Otherwise it rewrites from memory and you lose what was there.
Remember there is no draft: the skill the AI just edited is the skill your whole team gets on the very next call.
Uploading a package to update a skill replaces every attached file, so tell the AI which files you need kept.
create_key and create_member_key return the real key exactly once. Have the AI hand it straight to you, and save it.

Watching what the AI did

The Recent AI activity card on this very page lists the latest calls. Click View all agent logs to open the log already filtered to the AI agent kind.

Every write the AI makes also lands in the system Audit log, where whoever runs the server can cross-check it. The detail column keeps only identifying parameters (server name, skill name) and never holds skill content.

Because it writes real data, this key is capped at 60 calls per minute, tighter than a read key.