skills/mcporter/SKILL.md
Load when the user wants to call MCP tools, list MCP servers, manage MCP configuration, or interact with Model Context Protocol servers. Triggers include 'call MCP', 'list MCP servers', 'mcporter', 'MCP tool', 'run MCP', 'configure MCP'. Also load for ad-hoc MCP calls, OAuth setup, or code generation from MCP servers.
npx skillsauth add 0xrichardh/agent-skills mcporterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
CLI for calling MCP servers directly. Use npx mcporter — no global install required.
npx mcporter list # List all configured servers
npx mcporter list <server> # Show server tools with signatures
npx mcporter call <server>.<tool> key=val # Call a tool
npx mcporter config list # Show current configuration
Default config: $HOME/.config/mcporter/mcporter.json (override with --config <path> or MCPORTER_CONFIG).
Config supports JSONC (comments, trailing commas). Manage via CLI:
npx mcporter config add <name> <url> # Add HTTP server
npx mcporter config add <name> --command "npx ..." # Add stdio server
npx mcporter config remove <name> # Remove server
npx mcporter config import <kind> --copy # Import from editors
Env var interpolation in config: ${VAR}, ${VAR:-fallback}, $env:VAR. Secrets in headers, env, bearerTokenEnv resolve lazily at runtime.
npx mcporter call linear.create_comment issueId:ENG-123 body:'Looks good!' # Colon
npx mcporter call linear.create_comment issueId=ENG-123 body='Looks good!' # Equals
npx mcporter call 'linear.create_issue(title: "Bug", team: "ENG")' # Function
npx mcporter linear.list_issues # Shorthand
npx mcporter call https://mcp.linear.app/mcp.list_issues # Full URL
npx mcporter call --stdio "bun run ./server.ts" scrape url=https://example.com # Stdio
npx mcporter call <server>.<tool> --args '{"key": "value"}' # JSON
| Flag | Purpose |
|------|---------|
| --output json | Machine-readable output |
| --config <path> | Custom config file |
| --json | JSON output for list, auth |
| --schema | Full tool schema for list |
| --all-parameters | Show all optional params |
| --no-browser | Headless OAuth |
| --persist <file> | Save ad-hoc server to config |
| -- | Stop flag parsing |
npx mcporter auth <server> # Browser OAuth
npx mcporter auth <server> --no-browser # Headless (prints URL)
Call any MCP server without editing config:
npx mcporter list --http-url https://mcp.example.com/mcp --name my-server
npx mcporter call --stdio "npx -y some-mcp-server" tool_name arg=value
Add --persist config/mcporter.json to save for reuse.
Keep stateful servers alive between calls:
npx mcporter daemon start|status|stop|restart
Add "lifecycle": "keep-alive" to a server config entry.
Read references/codegen.md for CLI generation, TypeScript types, and runtime API.
listIssues → list_issues)npx mcporter firecrawl runs list firecrawl automaticallynpx mcporter linear.list_issues-- stops flag parsing for positional values starting with ----no-browser for headless--env KEY=val only for overrides--config > MCPORTER_CONFIG > ./config/mcporter.json > ~/.config/mcporter/mcporter.jsonAuthorization, env) resolve at runtime, not at parse timedevelopment
Load when the user needs web search, code examples, company intel, people lookup, or current information. Use for queries like 'search for', 'look up', 'find', 'what's the latest on', 'research company', 'code examples for'. Does not require a browser.
development
Load when the user wants to create, update, or refactor an agent skill, improve skill routing, split overlong skill instructions, or turn a repeated agent workflow into a reusable skill. Hand off to skill-creator for eval runs, packaging, and trigger-description optimization.
development
Find and inspect past OpenCode conversations stored in the local SQLite database. Use when the user asks to recall, search, find, or review a previous conversation, or asks "what did we talk about", "find that conversation where...", "show me past sessions", or any request to look up prior chat history.
tools
Comprehensive guide and resources for developing Logseq plugins. Use this skill when asked to: (1) Create a new Logseq plugin, (2) Implement features using the Logseq Plugin API (Editor, App, DB, UI), (3) Debug or refactor existing Logseq plugins, (4) Set up a development environment for Logseq plugins.