Skip to content

EXTERNAL-MCPS.md

Latest commit

 

History

History
72 lines (52 loc) · 4.53 KB

EXTERNAL-MCPS.md

File metadata and controls

72 lines (52 loc) · 4.53 KB

External MCPs

This is a sample list of external MCPs that you can use with Mini-A.

MCP Description Mini-A mcp parameter
mcp/dockerhub Interact with Docker Hub API (cmd: 'docker run --rm -i mcp/dockerhub')
mcp/wikipedia Interact with Wikipedia API (cmd: 'docker run --rm -i mcp/wikipedia-mcp')
mcp/duckduckgo Interact with DuckDuckGo API (cmd: 'docker run --rm -i mcp/duckduckgo')
mcp/fetch Fetch URLs (cmd: 'docker run --rm -i mcp/fetch')
mcp/openweather Interact with OpenWeather API (cmd: 'docker run --rm -i mcp/openweather')
mcp/markitdown Convert text to Markdown (cmd: 'docker run --rm -i mcp/markitdown')
mcp/time Get current time information (cmd: 'docker run --rm -i mcp/time')
mcp/aws-documentation Search AWS Documentation (cmd: 'docker run --rm -i mcp/aws-documentation')
public.ecr.aws/awslabs-mcp/awslabs/aws-api-mcp-server AWS API MCP Server (cmd: 'docker run --rm -i -e AWS_REGION=some-region -e AWS_ACCESS_KEY_ID=xxx -e AWS_SECRET_ACCESS_KEY=yyy public.ecr.aws/awslabs-mcp/awslabs/aws-api-mcp-server')
public.ecr.aws/awslabs-mcp/awslabs/eks-mcp-server AWS EKS MCP Server (cmd: 'docker run --rm -i -e AWS_REGION=some-region -e AWS_ACCESS_KEY_ID=xxx -e AWS_SECRET_ACCESS_KEY=yyy public.ecr.aws/awslabs-mcp/awslabs/eks-mcp-server')
public.ecr.aws/awslabs-mcp/awslabs/aws-pricing-mcp-server AWS Pricing MCP Server (cmd: 'docker run --rm -i -e AWS_REGION=some-region -e AWS_ACCESS_KEY_ID=xxx -e AWS_SECRET_ACCESS_KEY=yyy public.ecr.aws/awslabs-mcp/awslabs/aws-pricing-mcp-server')
public.ecr.aws/awslabs-mcp/awslabs/dynamodb-mcp-server AWS DynamoDB MCP Server (cmd: 'docker run --rm -i -e AWS_REGION=some-region -e AWS_ACCESS_KEY_ID=xxx -e AWS_SECRET_ACCESS_KEY=yyy public.ecr.aws/awslabs-mcp/awslabs/dynamodb-mcp-server')

For container based MCPs first pull the corresponding image with docker pull <image> before using it.

Check Docker MCP Hub Check AWS MCP Servers

Using external MCPs as HTTP remote

Some external MCP servers also expose an HTTP endpoint. When available, you can connect to them remotely the same way as Mini‑A’s built‑in MCPs that support onport.

Example (replace URL with the MCP’s endpoint):

mini-a goal="query the external MCP" \
	mcp="(type: remote, url: 'http://external.mcp.local:1234/mcp')" \
	rpm=20 tpm=80000 __format=md

Adjust rpm and tpm to stay within the MCP server's published limits.

Refer to the external MCP’s documentation to confirm whether it exposes an HTTP endpoint and the path (commonly /mcp).

When connecting to remote MCPs you may also need to provide credentials or API keys. Use standard oJob argument syntax, for example:

mini-a goal="use the private MCP" \
        mcp="(type: remote, url: 'https://example/mcp', headers: (authorization: 'Bearer ${MY_TOKEN}'))"

Prefer environment variables for sensitive data and confirm the external MCP's rate limits before automating high-frequency calls.

Aggregating multiple MCPs with mcp-proxy

When working with multiple external MCPs (or a mix of external and built-in MCPs), you can use mcp-proxy to aggregate them into a single unified endpoint. This simplifies configuration and provides a centralized interface for discovering and calling tools across all connected MCP servers.

Example: Aggregate external and built-in MCPs

# Start mcp-proxy aggregating Wikipedia, DuckDuckGo, and built-in mcp-time
ojob mcps/mcp-proxy.yaml onport=9000 \
  mcp="[(cmd: 'docker run --rm -i mcp/wikipedia-mcp'), (cmd: 'docker run --rm -i mcp/duckduckgo'), (cmd: 'ojob mcps/mcp-time.yaml')]"

# Now use the proxy with Mini-A
mini-a goal="search for information about Lisbon and tell me the current time there" \
  mcp="(type: remote, url: 'http://localhost:9000/mcp')" rpm=20

Benefits of using mcp-proxy

  • Unified discovery: List and search tools across all downstream MCPs with a single proxy-dispatch call.
  • Simplified configuration: Connect once to the proxy instead of managing multiple MCP connections.
  • Mixed sources: Combine STDIO MCPs (including Docker-based), HTTP remote MCPs, and built-in MCPs seamlessly.
  • Connection management: The proxy handles initialization, tool caching, and connection health for all downstream servers.

See README.md for detailed mcp-proxy documentation and additional examples.