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…

Apache-2.0Auto-check passedAgent Workflows

Install Agentcore Register

skills CLI
$ npx skills add agentic-community/mcp-gateway-registry --skill agentcore-register -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install agentic-community/mcp-gateway-registry agentcore-register --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
agentcore-register
GitHub stars
962
Token cost
~1.7k tokens
SKILL.md length
374 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
Apache-2.0

At a glance

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…

  • Works in 4 steps: Initialize the MCP session → List the tools → Generate the markdown file → …
  • Tasks that involve MCP servers
  • SKILL.md covers Steps, Tool Definition, Discovery Summary and Example
  • Calls curl; reaches novacoloritalianfinishes.agenthost.club

What it does

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.

When your agent uses it

  • Tasks that involve MCP servers
  • Tasks that involve Markdown

Example prompts

  • “Create record”
  • “/agentcore-register”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Initialize the MCP session
  2. List the tools
  3. Generate the markdown file
  4. Report to the user

What it can do on your machine

Read from SKILL.md and the folder at commit ec3a197. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • novacoloritalianfinishes.agenthost.club

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

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.

Safety

Auto-check passed

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.

SKILL.md

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.

Download SKILL.mdSave it as .claude/skills/agentcore-register/SKILL.md (or your agent's skills folder).
name
agentcore-register
description
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.
argument-hint
<mcp-server-url>

AgentCore Register

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.

Steps

1. Initialize the MCP session

Send the MCP initialize request and capture the response headers (for the session ID) and body (for server info).

bash
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>&1

Parse the response to extract:

  • serverInfo.name - the server name
  • serverInfo.version - the server version
  • protocolVersion - the MCP protocol version
  • capabilities - what the server supports

Extract the mcp-session-id header value from /tmp/_agentcore_mcp_headers.txt.

Error handling
  • If the curl request fails or times out, tell the user the server is unreachable and stop.
  • If the response is a 502/503/504, tell the user the server backend is down and stop.
  • If the response is HTML (not JSON), tell the user the URL may not be an MCP endpoint and stop.
2. List the tools

Using the session ID from step 1, send a tools/list request:

bash
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>&1

The response may be plain JSON or SSE-formatted (data: {...}). Handle both:

  • If the response starts with {, parse it directly as JSON.
  • If the response contains data: lines, extract the JSON from the data: line.

Parse the tools array from result.tools. For each tool, capture:

  • name
  • description
  • inputSchema (the full JSON schema object)
Show full SKILL.md (140 more words)Show less
3. Generate the markdown file

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:

markdown
# 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>"
    }
  ]
}

Tool Definition

Copy-paste the JSON below into the "Your Tool definition" editor:

json
{
  "tools": [
    <for each tool, include the full tool object with name, description, and inputSchema>
  ]
}

Discovery Summary

FieldValue
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.json
5. Report to the user

After generating the file, display:

  1. The path to the generated markdown file.
  2. A brief summary: server name, number of tools, transport type.
  3. Tell the user they can open the file and copy-paste each section into the AgentCore "Create record" form.

Example

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

Files

Just SKILL.md in .claude/skills/agentcore-register of agentic-community/mcp-gateway-registry.

Open the folder on GitHubat commit ec3a197

Compare with similar skills

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.

Agentcore Register compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agentcore Register this skillagentic-community/mcp-gateway-registry962—~1.7kAutomated safety check: PassApache-2.0
Update Component ReferenceNikiforovAll/claude-code-rules141—~2.1kAutomated safety check: PassApache-2.0
AWS Agentic AIzxkane/aws-skills3671 repos~2.5kAutomated safety check: PassMIT
OutlineVortiago/mcp-outline156—~818Automated safety check: PassMIT
Hcls Deploy Agentaws-samples/amazon-bedrock-agents-healthcare-lifesciences274—~813Automated safety check: PassMIT-0
AWS Strands Agents Agentcoresammcj/agentic-coding1621 repos~3kAutomated safety check: PassApache-2.0

Similar skills

  • 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.

    141 GitHub stars~2.1k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed
  • AWS Agentic AI

    zxkane/aws-skills

    AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale.

    367 GitHub starsUsed in 1 repo~2.5k tokens
    DevOps & CloudAuto-check passed
  • Outline

    Vortiago/mcp-outline

    Conventions and efficient workflows for Outline knowledge bases via mcp-outline tools.

    156 GitHub stars~818 tokensUpdated 2 mo ago
    Knowledge ManagementAuto-check passed
  • Hcls Deploy Agent

    aws-samples/amazon-bedrock-agents-healthcare-lifesciences

    Official

    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…

    274 GitHub stars~813 tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed
  • AWS Strands Agents Agentcore

    sammcj/agentic-coding

    A skill your agent uses when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents.

    162 GitHub starsUsed in 1 repo~3k tokens
    DevOps & CloudAuto-check passed
  • 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.

    279 GitHub stars~2.4k tokensUpdated 6 days ago
    Documents & OfficeAuto-check passed

More from agentic-community/mcp-gateway-registry

All 17 skills in this repo
  • Explainer

    agentic-community/mcp-gateway-registry

    Explain a GitHub issue or pull request at 100, 200, and 300 level.

    962 GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed
  • Debug

    agentic-community/mcp-gateway-registry

    Debug issues in the MCP Gateway Registry using first-principles thinking.

    962 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check: notes
  • Infra Sync

    agentic-community/mcp-gateway-registry

    Keep Terraform and CDK infrastructure in sync. An agent skill from agentic-community/mcp-gateway-registry.

    962 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Search Benchmark

    agentic-community/mcp-gateway-registry

    Generate a search quality benchmark for the AI Registry. An agent skill from agentic-community/mcp-gateway-registry.

    962 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Writing

    agentic-community/mcp-gateway-registry

    Write prose people will actually read. An agent skill from agentic-community/mcp-gateway-registry.

    962 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed
  • Benchmark Report

    agentic-community/mcp-gateway-registry

    Generate a benchmark report from stress test results (registration, API performance, search concurrency).

    962 GitHub stars~590 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Agentcore Register

What does Agentcore Register do?

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.

When should I use Agentcore Register?

Agentcore Register fits situations like: tasks that involve MCP servers; tasks that involve Markdown.

How do I install Agentcore Register in Claude Code?

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.

How do I install Agentcore Register in Codex?

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.

Can I use Agentcore Register in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Agentcore Register need to run?

Going by SKILL.md and its folder, Agentcore Register needs the command-line tools its instructions call (curl).

Does Agentcore Register access the network?

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.

Is Agentcore Register safe to install?

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.

What licence does Agentcore Register use?

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.

How many tokens does Agentcore Register use?

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.

What are the alternatives to Agentcore Register?

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.

Who maintains Agentcore Register?

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.