io.github.kody-w/rapp-agent-builder

by kody-w · remote · no sign-in to list tools · v1.0.0 · published by GitHub user kody-w

Turn an idea or meeting transcript into a working single-file AI agent, check it, use it right away.

Changes · 5

Compare Registry entry

8 tools: 5 change things and 3 only read.

Scanned Oct 21, 2026

Deletes or cancels0Claude Code: deny
Can't be undone0Claude Code: ask
Changes things5Claude Code: ask: see these tools
Only reads3Claude Code: allow: see these tools

3 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http rapp-agent-builder https://rapp-agent-builder.azurewebsites.net/mcp

Findings

Matches of fixed checks, with the text they matched.

3 warn

Warncheck_agent
The server marks "check_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
What this check looks for
Warnhow_to_run_agent
The server marks "how_to_run_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "how_to_run_agent" says "run": a word for a change.
What this check looks for
Warnshare_agent
The server marks "share_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 5Creates or changes something that can be changed back.Claude Code: ask

check_agentChecks a finished agent file against the template rules (manifest, naming, class, perform method, no hardcoded secrets).1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "check_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
  What this check looks for
Description, as the server wrote it
Checks a finished agent file against the template rules (manifest, naming, class, perform method, no hardcoded secrets). Call it on every agent you write, fix anything it reports, and call it again until it passes.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
how_to_run_agentOptional, for later: how to keep an agent running on the user's own computer with the free Brainstem.1 finding
Why it is in this group
- The name "how_to_run_agent" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "how_to_run_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "how_to_run_agent" says "run": a word for a change.
  What this check looks for
Description, as the server wrote it
Optional, for later: how to keep an agent running on the user's own computer with the free Brainstem. Only offer this after the user has used the agent in the chat and wants to keep it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
request_serviceUse when the person wants something none of these tools can do and says yes to passing the request on.No findings
Why it is in this group
- The name "request_service" says "request": a word for a change.
Description, as the server wrote it
Use when the person wants something none of these tools can do and says yes to passing the request on. Records only the request text they agree to send (no name or contact). Ask before calling it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
share_agentUse only when the user says they want to share an agent they built.1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "share_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
  What this check looks for
Description, as the server wrote it
Use only when the user says they want to share an agent they built. Checks the agent and scans it for personal details (emails, phone numbers, secrets), then explains how to publish it to the free public agent registry under their own GitHub account. Nothing is published by this tool.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
use_agent_hereUse this right after an agent passes check_agent, or whenever the user wants to try an agent.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
Use this right after an agent passes check_agent, or whenever the user wants to try an agent. Returns a short Python runner so you can run the agent in this chat with your own Python tool on the user's own data (pasted text, an uploaded spreadsheet, a list). Nothing to install. If Python is unavailable, apply the agent's logic yourself by reading its code. Ask the user for their real data, run the agent, and show the result in plain words.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false

Only reads 3Looks things up and changes nothing.Claude Code: allow

find_agentsSearches the public agent registry (about 1,700 single-file agents) for agents that already do what the user wants, for example when they ask 'is there an AI tool for...' or want a…No findings
Why it is in this group
- The name "find_agents" says "find": a word for reading.
Description, as the server wrote it
Searches the public agent registry (about 1,700 single-file agents) for agents that already do what the user wants, for example when they ask 'is there an AI tool for...' or want a ready-made automation instead of building one. Use it before building from scratch, or when the user asks whether an agent exists for a task.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_agent_codeReturns the full source of one agent from the registry, by its name (e.g.No findings
Why it is in this group
- The name "get_agent_code" says "get": a word for reading.
Description, as the server wrote it
Returns the full source of one agent from the registry, by its name (e.g. @bill/neuron_agent), so it can be read or adapted.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
get_agent_templateUse this when the user wants to build an AI agent, assistant, bot or automation from an idea, a repetitive task, a process description, or a meeting transcript (for example: automa…No findings
Why it is in this group
- The name "get_agent_template" says "get": a word for reading.
Description, as the server wrote it
Use this when the user wants to build an AI agent, assistant, bot or automation from an idea, a repetitive task, a process description, or a meeting transcript (for example: automate invoices, triage support tickets, summarize meetings, follow up with leads). Returns the official single-file agent template and its rules. Fill it in yourself from what the user described, then call check_agent on the finished file before showing it to the user. Then call use_agent_here so the user can use it right away in this chat.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http rapp-agent-builder https://rapp-agent-builder.azurewebsites.net/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__rapp-agent-builder__get_agent_template",
      "mcp__rapp-agent-builder__find_agents",
      "mcp__rapp-agent-builder__get_agent_code"
    ],
    "ask": [
      "mcp__rapp-agent-builder__check_agent",
      "mcp__rapp-agent-builder__use_agent_here",
      "mcp__rapp-agent-builder__how_to_run_agent",
      "mcp__rapp-agent-builder__share_agent",
      "mcp__rapp-agent-builder__request_service"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as rapp-agent-builder. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.kody-w/rapp-agent-builder/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.

For agents: Markdown · JSON · report this listing