servers / mcpc

mcpc MCP server

communitystdiolocalread onlyhealthy

Build agentic-MCP servers by composing existing MCP tools.


01Tools · 1

How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.

ToolRiskSide effectsApproval
mcpc-builder-agent
Agentic tool `mcpc-builder-agent` that executes tasks by calling its tools, following the <rules/> and using the <format/>. Builds custom agentic tools from mcpc.tech registry. <tool name="mcpc-builder_search_mcp_servers"/> <tool name="mcpc-builder_get_env_var_schemas"/> <tool name="mcpc-builder_compose_mcpc_config"/> <rules> 1. **First call**: Use `man` to get tool schemas and full manual 2. **Execute tools**: Use tool name in `tool` and parameters in `args` </rules> <format> Get manual + schemas: `{ "tool": "man", "args": { "tools": ["tool1"], "manual": true } }` Execute a tool: `{ "tool": "tool_name", "args": { /* parameters */ } }` </format>
readfalseunknown

02Install & source
npx -y @mcpc-tech/builder
npx
npx -y @mcpc-tech/cli
npx

05Provenance & freshness
sourcesGitHub repo search [p4]
last_checked2026-08-16 18:46Z
next_check2026-08-16 21:46Z
cadenceevery 3h
verifiedhandshake:failed metadata:passed handshake:failed metadata:passed handshake:failed metadata:passed handshake:failed metadata:passed handshake:failed metadata:passed
index_statusindex8 unique facts >= 5

06Badge

Add the “as seen on MCPExplorer” badge to your README. mcpc MCP — as seen on mcpexplorer.com

[![mcpc MCP — as seen on mcpexplorer.com](https://mcpexplorer.com/badge/mcpc.svg)](https://mcpexplorer.com/servers/mcpc)

Next step

This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.

Explore loadouts →