Bridge Any MCP Server with Mcporter: The Universal Tool Caller for Clawdbot

The Model Context Protocol (MCP) is quickly becoming the standard way for AI agents to connect with external tools and services. But managing MCP servers—configuring them, authenticating, and calling their tools—can be tedious. Enter Mcporter: an official ClawdHub skill that gives your Clawdbot agent a unified CLI for discovering, calling, and managing MCP servers.

What Problem Does Mcporter Solve?

If you've worked with MCP servers before, you know the pain:

Fragmented configuration: Each server might need different setup
Auth headaches: OAuth flows, API keys, tokens scattered everywhere
Discovery friction: Finding available tools and their schemas
No unified interface: Switching between HTTP and stdio servers requires different approaches

Mcporter wraps all of this into a single CLI that your agent can use. List tools, call them with natural syntax, manage auth—all from one interface.

Installation

Install Mcporter from ClawdHub:

npx clawdhub@latest install mcporter

Or install the underlying CLI directly:

npm i -g mcporter

Quick Start: List and Call

List all configured MCP servers:

mcporter list

See what tools a server exposes:

mcporter list linear --schema

Call a tool with key=value syntax:

mcporter call linear.list_issues team=ENG limit:5

The selector format is server.tool, and parameters use key=value (strings) or key:value (other types like numbers/booleans).

Usage Examples

1. Direct URL Calls

Don't have a server configured? Call any MCP endpoint directly:

mcporter call https://api.example.com/mcp.fetch url=https://example.com

2. Stdio Servers

Run a local MCP server via stdio:

mcporter call --stdio "bun run ./server.ts" scrape url=https://example.com

This is perfect for testing local servers or using ones that aren't HTTP-based.

3. Function-Style Syntax

For more complex calls, use function syntax:

mcporter call "linear.create_issue(title: \"New bug\", priority: 2)"

4. JSON Payloads

When you need precise control, pass raw JSON:

mcporter call linear.create_issue --args '{ "title": "Bug report", "description": "Details here" }'

Authentication

Mcporter handles OAuth and token-based auth:

Start OAuth flow:

mcporter auth linear

Reset and re-authenticate:

mcporter auth linear --reset

Configuration Management

Manage your MCP server configs:

# List configured servers
mcporter config list

# Add a new server
mcporter config add myserver https://myserver.example.com/mcp

# Import from external config
mcporter config import

# Login to ClawdHub registry
mcporter config login

Configuration lives in ./config/mcporter.json by default (override with --config).

Advanced: Code Generation

Mcporter can generate typed CLIs and TypeScript bindings from MCP servers:

Generate a CLI wrapper:

mcporter generate-cli --server linear

Generate TypeScript types:

mcporter emit-ts linear --mode types

Inspect a generated CLI:

mcporter inspect-cli ./my-cli.js --json

Daemon Mode

For faster repeated calls, run Mcporter as a daemon:

mcporter daemon start
mcporter daemon status
mcporter daemon stop

This keeps connections warm and reduces latency for frequent tool calls.

Pro Tips

Always use --output json when calling from scripts or agents—machine-readable output is cleaner to parse
Combine with other skills: Use Mcporter to call external MCP servers, then pipe results to other ClawdHub skills
Local-first development: Use --stdio mode to test your own MCP servers before deploying them

Conclusion

Mcporter turns MCP server management from a chore into a one-liner. Whether you're listing tools, handling OAuth, or generating type-safe clients, it's the Swiss Army knife for MCP integration in Clawdbot.

Links:

Happy porting! 🦞