MCP.so
Sign In

MCP-testing: OpenWebUI + mcpo Integration

@cycloarcane

Basic information

Category

Other

Transports

stdio

Author

cycloarcane

About MCP-testing: OpenWebUI + mcpo Integration

A repository to test MCP servers and interations.

MCP-testing: OpenWebUI + mcpo Integration config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "MCP-testing": {
      "command": "uvx",
      "args": [
        "mcpo",
        "--port",
        "8000",
        "--api-key",
        "dev123",
        "--config",
        "./config.json"
      ]
    }
  }
}

MCP-testing: OpenWebUI + mcpo Integration tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is MCP-testing: OpenWebUI + mcpo Integration?

This repository is for experimenting with running MCP tools (premade and custom) via mcpo and integrating them cleanly with OpenWebUI. Its current goal is to set up and successfully call the premade mcp-server-time tool using mcpo’s config-based proxy.

How to use MCP-testing: OpenWebUI + mcpo Integration?

Launch mcpo with uvx mcpo --port 8000 --api-key dev123 --config ./config.json. Then configure OpenWebUI with Base URL http://127.0.0.1:8000/time and OpenAPI URL /openapi.json. Ensure the chat tool toggle is enabled and the chat model supports function calling (e.g., GPT‑4, Mistral‑7B‑func, Qwen3).

Key features of MCP-testing: OpenWebUI + mcpo Integration

  • Premade MCP tool integration via mcpo proxy
  • Config‑based tool mounting with JSON configuration
  • API key authentication for mcpo
  • Compatible with OpenWebUI’s custom tool system
  • Supports tool‑specific endpoints (e.g., /time)

Use cases of MCP-testing: OpenWebUI + mcpo Integration

  • Experimenting with MCP tool integration in OpenWebUI
  • Running a single premade MCP tool through mcpo
  • Testing config‑based proxy setup for MCP tools
  • Learning how to correctly configure OpenWebUI base URLs

Frequently asked questions

1

How do I fix a 401 Unauthorized error?

Ensure you use the `Authorization: Bearer dev123` header or input the API key into OpenWebUI’s API key field.

2

Why do I get a 404 Not Found?

Double‑check the tool mount path. In config mode, tool functions are under `/tool-name/function-name` (e.g., `/time/get_current_time`).

3

What should I do if the tool doesn’t respond?

Verify the Base URL in OpenWebUI is correct. It must point to the tool’s mount path (e.g., `http://127.0.0.1:8000/time`), not the root.

Comments

More Other MCP servers