Update Component Reference
NikiforovAll/claude-code-rules
This skill should be used when the user wants to add components (commands, agents, skills, hooks, or MCP servers) to the Component Reference section of the website.
Given an MCP server URL, probe the server via curl to discover its metadata and tools, then generate a markdown file with copy-pasteable content for each field in the Amazon Bedrock AgentCore…
$ npx skills add agentic-community/mcp-gateway-registry --skill agentcore-register -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agentic-community/mcp-gateway-registry agentcore-register --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/agentcore-register .claude/skills/agentcore-register && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "agentcore-register" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/agentcore-register into .claude/skills/agentcore-register/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore-register", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/agentcore-registerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add agentic-community/mcp-gateway-registry --skill agentcore-register -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agentic-community/mcp-gateway-registry agentcore-register --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/agentcore-register .agents/skills/agentcore-register && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agentcore-register" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/agentcore-register into .agents/skills/agentcore-register/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore-register", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agentic-community/mcp-gateway-registry --skill agentcore-register -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agentic-community/mcp-gateway-registry agentcore-register --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/agentcore-register .cursor/skills/agentcore-register && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "agentcore-register" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/agentcore-register into .cursor/skills/agentcore-register/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore-register", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/agentic-community/mcp-gateway-registry.git --path .claude/skills/agentcore-register--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add agentic-community/mcp-gateway-registry --skill agentcore-register -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agentic-community/mcp-gateway-registry agentcore-register --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/agentcore-register .gemini/skills/agentcore-register && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "agentcore-register" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/agentcore-register into .gemini/skills/agentcore-register/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore-register", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install agentic-community/mcp-gateway-registry agentcore-registerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add agentic-community/mcp-gateway-registry --skill agentcore-register -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/agentcore-register .github/skills/agentcore-register && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "agentcore-register" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/agentcore-register into .github/skills/agentcore-register/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore-register", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agentic-community/mcp-gateway-registry --skill agentcore-register -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agentic-community/mcp-gateway-registry agentcore-register --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/agentcore-register .opencode/skills/agentcore-register && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "agentcore-register" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/agentcore-register into .opencode/skills/agentcore-register/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore-register", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
agentcore-registerGiven an MCP server URL, probe the server via curl to discover its metadata and tools, then generate a markdown file with copy-pasteable content for each field in the Amazon Bedrock AgentCore…
Agentcore Register is an agent skill from agentic-community/mcp-gateway-registry. Given an MCP server URL, probe the server via curl to discover its metadata and tools, then generate a markdown file with copy-pasteable content for each field in the Amazon Bedrock AgentCore "Create record" form.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers and Markdown. It works with Model Context Protocol and Amazon Bedrock. The repository describes itself as: Enterprise-ready MCP Gateway & Registry that centralizes AI development tools with secure OAuth authentication, dynamic tool discovery, and unified access for both autonomous AI… The licence is Apache-2.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit ec3a197. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
curlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
novacoloritalianfinishes.agenthost.clubFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Agentcore Register loads about 1.7k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 374 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from agentic-community/mcp-gateway-registry at commit ec3a197, republished under its Apache-2.0 licence (© agentic-community). 374 words, ~1,723 tokens.
.claude/skills/agentcore-register/SKILL.md (or your agent's skills folder).Given a remote MCP server URL, probe it to discover server info and tools, then generate a markdown file containing copy-pasteable values for every field in the Amazon Bedrock AgentCore Create record form.
The MCP server URL is provided as $ARGUMENTS.
If $ARGUMENTS is empty, ask the user for the MCP server URL using AskUserQuestion.
Send the MCP initialize request and capture the response headers (for the session ID) and body (for server info).
curl -s --max-time 15 -D /tmp/_agentcore_mcp_headers.txt \
-X POST "$MCP_URL" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2024-11-05",
"capabilities": {},
"clientInfo": {"name": "agentcore-register", "version": "1.0.0"}
}
}' > /tmp/_agentcore_mcp_init.json 2>&1Parse the response to extract:
serverInfo.name - the server nameserverInfo.version - the server versionprotocolVersion - the MCP protocol versioncapabilities - what the server supportsExtract the mcp-session-id header value from /tmp/_agentcore_mcp_headers.txt.
Using the session ID from step 1, send a tools/list request:
SESSION_ID=$(grep -i 'mcp-session-id' /tmp/_agentcore_mcp_headers.txt | awk '{print $2}' | tr -d '\r')
curl -s --max-time 15 \
-X POST "$MCP_URL" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc": "2.0", "id": 3, "method": "tools/list", "params": {}}' \
> /tmp/_agentcore_mcp_tools.json 2>&1The response may be plain JSON or SSE-formatted (data: {...}). Handle both:
{, parse it directly as JSON.data: lines, extract the JSON from the data: line.Parse the tools array from result.tools. For each tool, capture:
namedescriptioninputSchema (the full JSON schema object)Create a markdown file at .scratchpad/agentcore-register-<server-name>.md with all the values the user needs to copy-paste into the AgentCore form.
Use this exact template, replacing placeholders with the discovered values:
# AgentCore Registry Record: <server_name>
*Generated: <current date>*
*Source: <MCP_URL>*
---
## Record Details
**Name:**<server_name as a valid record ID, e.g. record_novacolor_finishes>
**Description:**<server description derived from tools and server name, 1-2 sentences>
**Record version:**<server version, e.g. 0.1>
**Record type:** MCP
---
## MCP Server Definition
Copy-paste the JSON below into the "Your MCP server definition" editor:
```json
{
"name": "<namespace/slug, must match ^[a-zA-Z0-9.-]+/[a-zA-Z0-9._-]+$>",
"description": "<max 100 chars, concise description>",
"version": "<version>",
"remotes": [
{
"type": "<transport type, e.g. streamable-http>",
"url": "<MCP_URL>"
}
]
}Copy-paste the JSON below into the "Your Tool definition" editor:
{
"tools": [
<for each tool, include the full tool object with name, description, and inputSchema>
]
}| Field | Value |
|---|---|
| Server name | <serverInfo.name> |
| Version | <version> |
| Protocol | <protocolVersion> |
| Transport | <transport type> |
| URL | <MCP_URL> |
| Tools | <comma-separated tool names> |
| Capabilities | <comma-separated capabilities> |
#### Rules for populating the template
- **Record name**: Convert the server name to a valid AgentCore record ID. Use lowercase, replace spaces and hyphens with underscores, prefix with `record_`. Only use letters, digits, underscores. Example: `record_novacolor_finishes`.
- **Description**: Write a concise 1-2 sentence description based on the server name and tool names/descriptions.
- **Transport**: Determine from how the server responded:
- If the initialize response included `mcp-session-id` header and responded to POST with JSON, use `streamable-http`.
- If the server used SSE (event-stream responses for initialize), use `sse`.
- Default to `streamable-http` for remote HTTP servers.
- **MCP server definition JSON**: Must include `name`, `description`, `version`, and `remotes` fields. The `remotes` array contains the transport type and URL so that the AgentCore sync can extract `proxy_pass_url` correctly via `remotes[0].url`.
- **name** MUST match the pattern `^[a-zA-Z0-9.-]+/[a-zA-Z0-9._-]+$` (namespace/name format). Derive the namespace from the server's domain (e.g., `com.agenthost` for `agenthost.club`, `io.github.user` for GitHub). Example: `com.agenthost/novacolor-italian-finishes`.
- **description** MUST be 100 characters or fewer. Keep it concise.
- **remotes** MUST be an array with at least one object containing `type` (transport type) and `url` (the MCP endpoint URL). Do NOT use top-level `url` and `transport` fields -- use the `remotes` array format instead.
- **Tool definition JSON**: Include the complete tool objects exactly as returned by the server, wrapped in a `{"tools": [...]}` envelope.
- **Tool inputSchema**: Include the full inputSchema for each tool exactly as returned by the server. Do NOT simplify or omit properties.
### 4. Cleanup
Remove temporary files:
```bash
rm -f /tmp/_agentcore_mcp_headers.txt /tmp/_agentcore_mcp_init.json /tmp/_agentcore_mcp_tools.jsonAfter generating the file, display:
User: /agentcore-register https://novacoloritalianfinishes.agenthost.club/mcp
Output:
Generated `.scratchpad/agentcore-register-novacolor.md`
Summary:
- Server: some-agent (v0.1)
- Transport: streamable-http
- Tools: 3 (search_site_products, search, fetch)
Open the file and copy-paste each section into the AgentCore "Create record" form.© agentic-community, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/agentcore-register of agentic-community/mcp-gateway-registry.
Open the folder on GitHubat commit ec3a197
Agentcore Register next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Agentcore Register this skillagentic-community/mcp-gateway-registry | 962 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Update Component ReferenceNikiforovAll/claude-code-rules | 141 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| AWS Agentic AIzxkane/aws-skills | 367 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| OutlineVortiago/mcp-outline | 156 | — | ~818 | Automated safety check: Pass | MIT | |
| Hcls Deploy Agentaws-samples/amazon-bedrock-agents-healthcare-lifesciences | 274 | — | ~813 | Automated safety check: Pass | MIT-0 | |
| AWS Strands Agents Agentcoresammcj/agentic-coding | 162 | 1 repos | ~3k | Automated safety check: Pass | Apache-2.0 |
NikiforovAll/claude-code-rules
This skill should be used when the user wants to add components (commands, agents, skills, hooks, or MCP servers) to the Component Reference section of the website.
zxkane/aws-skills
AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale.
Vortiago/mcp-outline
Conventions and efficient workflows for Outline knowledge bases via mcp-outline tools.
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
A skill your agent uses when a developer wants to deploy an HCLS agent to Amazon Bedrock AgentCore, configure Gateway tools as MCP endpoints, set up authentication with Cognito, configure memory, or…
sammcj/agentic-coding
A skill your agent uses when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents.
testdouble/han
Publishes a local Markdown file to a user-specified Confluence location, creating a new page or updating an existing one through the Atlassian MCP server.
agentic-community/mcp-gateway-registry
Explain a GitHub issue or pull request at 100, 200, and 300 level.
agentic-community/mcp-gateway-registry
Debug issues in the MCP Gateway Registry using first-principles thinking.
agentic-community/mcp-gateway-registry
Keep Terraform and CDK infrastructure in sync. An agent skill from agentic-community/mcp-gateway-registry.
agentic-community/mcp-gateway-registry
Generate a search quality benchmark for the AI Registry. An agent skill from agentic-community/mcp-gateway-registry.
agentic-community/mcp-gateway-registry
Write prose people will actually read. An agent skill from agentic-community/mcp-gateway-registry.
agentic-community/mcp-gateway-registry
Generate a benchmark report from stress test results (registration, API performance, search concurrency).
Works with
Categories
Given an MCP server URL, probe the server via curl to discover its metadata and tools, then generate a markdown file with copy-pasteable content for each field in the Amazon Bedrock AgentCore…. Agentcore Register is an agent skill from agentic-community/mcp-gateway-registry. Given an MCP server URL, probe the server via curl to discover its metadata and tools, then generate a markdown file with copy-pasteable content for each field in the Amazon Bedrock AgentCore "Create record" form.
Agentcore Register fits situations like: tasks that involve MCP servers; tasks that involve Markdown.
Run `npx skills add agentic-community/mcp-gateway-registry --skill agentcore-register -a claude-code`. Or copy the skill folder (.claude/skills/agentcore-register in agentic-community/mcp-gateway-registry) into .claude/skills/agentcore-register in your project. Claude Code loads it when a task matches its description.
Run `npx skills add agentic-community/mcp-gateway-registry --skill agentcore-register -a codex`. Or copy the skill folder (.claude/skills/agentcore-register in agentic-community/mcp-gateway-registry) into .agents/skills/agentcore-register in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agentic-community/mcp-gateway-registry --skill agentcore-register -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agentcore-register, .gemini/skills/agentcore-register, .github/skills/agentcore-register and .opencode/skills/agentcore-register in your project.
Going by SKILL.md and its folder, Agentcore Register needs the command-line tools its instructions call (curl).
SKILL.md names 1 domain. In commands or code: novacoloritalianfinishes.agenthost.club; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Agentcore Register is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Agentcore Register: Update Component Reference (NikiforovAll/claude-code-rules, 141 stars), AWS Agentic AI (zxkane/aws-skills, 367 stars), Outline (Vortiago/mcp-outline, 156 stars) and Hcls Deploy Agent (aws-samples/amazon-bedrock-agents-healthcare-lifesciences, 274 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
agentic-community (a GitHub organization) maintains it in agentic-community/mcp-gateway-registry, which has 962 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.
Source: agentic-community/mcp-gateway-registry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.