my-mcp-server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@my-mcp-serverlist all items"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
my-cmp-server
A FastMCP server that wraps a REST API as MCP tools.
Overview
This is a FastMCP server that exposes a REST API as a set of MCP (Model Context Protocol) tools. AI agents and LLMs can invoke these tools to interact with the upstream API.
Prerequisites
Python 3.11+
The upstream API running at
https://localhost:8080
Setup
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
### Run
```bash
python3 mcp_server.pyThe server starts on http://0.0.0.0:8000/mcp using the
streamable HTTP transport.
Related MCP server: e2e-mcp-test
Container Build
docker build -t my-cmp-server .
docker run -p 8000:8000 my-cmp-serverCI/CD with Pipelines as Code (Tekton)
This project uses Pipelines as Code (PAC) for fully automated CI/CD on
Openshift. No manual setup is required -- every push to main automatically
builds the container image and deploys to Openshift.
The pipeline definition lives in .tekton/push.yaml and performs:
Clone -- fetches the repository source
Build -- biulds the container image with buildah and pushes to the OpenShift internal registry
Deploy -- applies the deployment manifests and rolls out the new version.
How it works
A GitHub webhook (created automatically by the RHDH template) sends push events
to the Pipelines as Code controller on Openshift. PAC reads .tekton/push.yaml
from the repo and creates a PipelineRun automatically.
Manual Deployment (without pipeline)
Apply the included manifests directly:
oc apply -f deploy/deployment.yamlThis creates a Deployment, Service, and Route in the mcp-servers
namespace. The Route provides a TLS-terminated public endpoint.
Customization
Edit mcp_server.py to replace the placeholder tools (list_items,
get_item,create_item) with tools that match your actual API endpoints.
Each @mcp.tool function maps to one REST endpoint:
HTTP Method | MCP Tool Pattern |
GET (list) | Tool that returns a list of resources |
GET (by id) | Tool that returns a single resource |
POST | Tool that creates a resource |
PATCH / PUT | Tool that updates a resource |
DELETE | Tool that removes a resource |
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server exposing the Backtest360 engine API as tools for AI agents.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA universal MCP server that connects any REST API to AI assistants via OpenAPI or Postman specifications. It enables dynamic tool creation with GraphQL-style field selection and automatic schema inference for efficient data retrieval.8 npm6-
- FlicenseNot gradedqualityCmaintenanceAn end-to-end test MCP server built with FastMCP that exposes a REST API as a set of tools for AI agents. It enables LLMs to perform CRUD operations on an upstream API by mapping HTTP methods to MCP tools.-
- FlicenseNot gradedqualityNot gradedmaintenanceA FastMCP server that exposes REST API endpoints as Model Context Protocol tools for AI agents. It provides a template for wrapping upstream APIs and includes deployment support for Docker and OpenShift.-
- FlicenseNot gradedqualityDmaintenanceA standalone MCP server that exposes API endpoints as tools for AI assistants, using SSE transport.-