Mcp

Skill pecigonzalo/agent-skills/skills/mcp

Personal agent skills

Install

npx -y skills add pecigonzalo/agent-skills --skill mcp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Discover, configure, and call MCP (Model Context Protocol) servers. Use this when interacting with MCP tools or resources in Pi, inspecting schemas, authenticating servers, trying ad-hoc endpoints, or generating typed MCP clients and CLIs.

SKILL.md

4.3 KB, as published. Nobody here has run it

MCP

For normal MCP tool calls, prefer the typescript tool and its host.mcp bridge. It makes filtering, pagination, batching, and further processing straightforward. Use mcporter only for discovery, configuration, authentication, diagnostics, or one-off ad-hoc calls.

TypeScript workflows

Once the relevant server and tool are known, call it through host.mcp:

const result = await host.mcp.call({
  server: "linear",
  tool: "list_issues",
  args: { assignee: "me", limit: 50 },
});

const { issues } = JSON.parse(result.text!);
return issues;

Use result.text as the tool response. Parse it only when the tool returns JSON. Use host.mcp.listTools({ server }) to inspect a known server when necessary.

mcporter discovery and administration

Use Pi's MCP config at ~/.pi/agent/mcp.json so CLI calls match /mcp status and host.mcp.

bunx mcporter --config ~/.pi/agent/mcp.json <command>

If Bun is unavailable, use npx -y mcporter --config ~/.pi/agent/mcp.json <command>.

Discovery

Start by listing configured servers:

bunx mcporter --config ~/.pi/agent/mcp.json list

Inspect likely servers compactly before loading full schemas:

bunx mcporter --config ~/.pi/agent/mcp.json list <server> --brief
bunx mcporter --config ~/.pi/agent/mcp.json list <server.tool> --brief

Load full schemas only when needed to call a tool accurately:

bunx mcporter --config ~/.pi/agent/mcp.json list <server> --schema
bunx mcporter --config ~/.pi/agent/mcp.json list <server.tool> --schema

Ad-hoc CLI calls

Use the CLI only for manual or one-off calls. Use shell-friendly key/value arguments for simple calls:

bunx mcporter --config ~/.pi/agent/mcp.json call <server.tool> query="React hooks docs" limit:5

Use function-call syntax for nested or complex arguments:

bunx mcporter --config ~/.pi/agent/mcp.json call 'server.tool(name: "value", options: { limit: 5 })'

For file-backed text arguments, use key=@path.

Resources

List or read MCP resources:

bunx mcporter --config ~/.pi/agent/mcp.json resource <server>
bunx mcporter --config ~/.pi/agent/mcp.json resource <server> <uri>

Config and auth

Inspect and manage MCP configuration:

bunx mcporter --config ~/.pi/agent/mcp.json config list
bunx mcporter --config ~/.pi/agent/mcp.json config get <server>
bunx mcporter --config ~/.pi/agent/mcp.json config add <name> <url-or-command>
bunx mcporter --config ~/.pi/agent/mcp.json config import <kind>

Authenticate OAuth-backed servers:

bunx mcporter --config ~/.pi/agent/mcp.json auth <server-or-url>

Use --no-browser on headless hosts and keep the process alive until the browser redirect completes.

Ad-hoc servers

Try HTTP or stdio servers without editing config:

bunx mcporter --config ~/.pi/agent/mcp.json list https://mcp.example.com/mcp --brief
bunx mcporter --config ~/.pi/agent/mcp.json list --http-url https://mcp.example.com/mcp --name example --brief
bunx mcporter --config ~/.pi/agent/mcp.json call 'https://mcp.example.com/mcp.tool(arg: "value")'
bunx mcporter --config ~/.pi/agent/mcp.json list --stdio "bun run ./server.ts" --name local-tools

Add --persist config/mcporter.json when the server should become reusable by name.

Daemon diagnostics

mcporter can keep configured lifecycle: "keep-alive" servers warm and starts daemon-managed servers on demand. Check status only when diagnosing connection or startup issues:

bunx mcporter --config ~/.pi/agent/mcp.json daemon status

Generated TypeScript clients and CLIs

For stable or repeated workflows, generate typed clients or dedicated CLIs instead of hand-writing calls:

bunx mcporter --config ~/.pi/agent/mcp.json emit-ts <server> --mode client --out clients/<server>.ts
bunx mcporter --config ~/.pi/agent/mcp.json generate-cli <server> --bundle dist/<server>.js