df667e0db8
- web/: Local chat UI (Express + WS → Codex bridge) - openwebui/: Preset, pipelines, knowledge manifest - Dockerfile + docker-compose.yml - Updated README with 3 frontend options - CLI-agnostic: works with Codex, Claude Code, Kiro, Gemini
1.7 KiB
1.7 KiB
name, description, homepage
| name | description | homepage |
|---|---|---|
| mcporter | Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation. | http://mcporter.dev |
mcporter
Use mcporter to work with MCP servers directly.
⚠️ CRITICAL EXECUTION RULE:
Whenever you run mcporter, you MUST source the local .env file first so mcporter.json can interpolate the required API keys. Always run it as a chained command like this:
set -a && source .env && set +a && mcporter --config config/mcporter.json call <server.tool> key=value
Quick start
mcporter listmcporter list <server> --schemamcporter call <server.tool> key=value
Call tools
- Selector:
mcporter call linear.list_issues team=ENG limit:5 - Function syntax:
mcporter call "linear.create_issue(title: \"Bug\")" - Full URL:
mcporter call https://api.example.com/mcp.fetch url:https://example.com - Stdio:
mcporter call --stdio "bun run ./server.ts" scrape url=https://example.com - JSON payload:
mcporter call <server.tool> --args '{"limit":5}'
Auth + config
- OAuth:
mcporter auth <server | url> [--reset] - Config:
mcporter config list|get|add|remove|import|login|logout
Daemon
mcporter daemon start|status|stop|restart
Codegen
- CLI:
mcporter generate-cli --server <name>or--command <url> - Inspect:
mcporter inspect-cli <path> [--json] - TS:
mcporter emit-ts <server> --mode client|types
Notes
- config file is located at
config/mcporter.jsonyou may have to resolve a different relative path depending on your context - Prefer
--output jsonfor machine-readable results. - Always use
--args '{...}'(JSON payload) for Atlassian calls with complex/nested fields.