About API Wrapper MCP
API Wrapper MCP is an MCP server published by gomcpgo in the Developer Tools category: create MCP server for any API. It has been installed 0 times through Conduid.
The repository has 18 stars and 11 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx api-wrapper-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about API Wrapper MCP
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
API Wrapper MCP Server
This is a generic API wrapper server for the Model Context Protocol (MCP). It allows you to easily wrap REST APIs as MCP tools that can be accessed by Claude and other MCP clients.
Features
- Easy YAML configuration for multiple API endpoints
- Support for both GET and POST requests
- Parameter validation and default values
- Authentication via environment variables
- Custom timeouts for API calls
Usage
- Create a YAML configuration file defining your API endpoints (see
example-config.yaml) - Set any required API tokens as environment variables
- Run the server with your config file:
# Build the server
go build -o api_wrapper
# Run with your config
./api_wrapper my-apis.yaml
Configuration Format
The configuration file uses YAML format with the following structure:
# Server info
server:
name: "API Gateway MCP"
description: "Generic API gateway that wraps REST APIs as MCP tools"
version: "1.0.0"
# Authentication
auth:
token_env_var: "API_GATEWAY_TOKEN" # Environment variable for the API token
# Tool definitions
tools:
- name: "tool-name"
description: "Tool description"
endpoint: "https://api.example.com/endpoint"
method: "POST" # or "GET"
timeout: 30 # in seconds
template: |
{
"param1": "{{variable1}}",
"param2": {{variable2}}
}
# For GET requests, use query_params
query_params:
param1: "{{variable1}}"
param2: "{{variable2}}"
parameters:
variable1:
type: "string"
description: "Description of variable1"
required: true
variable2:
type: "number"
description: "Description of variable2"
default: 10
Claude Desktop Integration
To use with Claude Desktop, add the following to your claude_desktop_config.json:
{
"mcpServers": {
"api-wrapper": {
"command": "path/to/api_wrapper",
"args": ["path/to/your-config.yaml"],
"env": {
"API_GATEWAY_TOKEN": "your-api-token"
}
}
}
}
Examples
Check out example-config.yaml for sample API configurations.
Environment Variables
- Set the main authentication token using the environment variable specified in the
auth.token_env_varfield. - You can also reference other environment variables in your templates using
{{env:VARIABLE_NAME}}syntax.
README mirrored from the source repository 4 months ago. The original is authoritative.