mcp-one

Created By
MCPHubClouda year ago
A unified All-in-One entrance for mcpservers, which manages various types of mcpservers.
Overview

What is mcp-one?

mcp-one is a unified All-in-One entrance for managing various types of mcpservers, providing a streamlined interface for users to interact with multiple servers.

How to use mcp-one?

To use mcp-one, you need to configure it with a YAML file and run the server using the command: ./mcp-one -c ./mcpone-config.yaml --baseurl 0.0.0.0:9090. You can also add an SSE client to your application to connect to the server.

Key features of mcp-one?

  • Unified management for multiple mcpservers
  • Easy configuration through YAML files
  • Support for adding new servers dynamically
  • Docker deployment options

Use cases of mcp-one?

  1. Managing multiple mcpservers from a single interface.
  2. Deploying mcpservers in a Docker environment.
  3. Customizing server configurations for different applications.

FAQ from mcp-one?

  • What types of servers does mcp-one support?

mcp-one supports various mcpservers, including time-mcp and mcp-server-fetch, with the ability to add more through configuration.

  • Is mcp-one easy to deploy?

Yes! mcp-one can be easily deployed using Docker or by building from source.

  • Can I contribute to mcp-one?

Absolutely! Contributions are welcome, and you can submit PRs or issues to enhance the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCPHubCloud
Star
3
Language
Go
License
MIT license
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago