Here comes the mcpSrvr — A Shared Host for MCP Tools
mcpSrvr lets you describe your Http API using OpenAPI specification and registers every path method as an MCP Tool on a remote server. Once published, the tool is available to MCP Clients compatible with Streamable HTTP transport.
{
"openapi": "3.0.0",
"info": {
"title": "Simple API",
"version": "1.0.0"
},
"servers": [
{
"url": "https://api.configry.app"
}
],
"paths": {
"/config/{code}": {
"get": {
"summary": "Get config data for the given code",
"operationId": "getConfig",
"parameters": [
{
"name": "code",
"in": "path",
"description": "Configuration Code",
"required": true,
"schema": {
"type": "string"
}
},
{
"name": "x-api-key",
"in": "header",
"description": "Api Key",
"required": true,
"schema": {
"type": "string"
}
}
],
"responses": {
"200": {
"description": "Successful response",
"content": {
"application/json": {
"schema": {
"type": "object",
"properties": {
"code": {
"type": "string"
},
"label": {
"type": "string"
},
"config": {
"type": "object"
}
}
}
}
}
}
}
}
}
}
}How It Works
Plug your Http API resource
Every resource method provided in the OpenAPI document is registered as an MCP Server Tool with a unique name. When an MCP Client executes a tool, each execution results in making a call to the mapped method of the corresponding Http API path - along with the defined parameters, including any header parameters.
Response from the API resource is returned to MCP Client as a 'text' result.
Authorization is handled by the underlying API resource. mcpSrvr is not involved in the process.