Zyla Labs MCP (84f50b)

MCPAI代理

提供方 未标注

AI代理 HTTP · 远程 OAuth 授权 社区 / 第三方

全面解析Zyla Api Hub MCP ServerMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,Zyla Api Hub MCP Server能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

Zyla Labs MCP (84f50b) 属于AI代理类 MCP 服务器,HTTP · 远程,OAuth 授权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式HTTP · 远程 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

HTTP · 远程 OAuth 授权
连远程 HTTPS 端点,通常为 Streamable HTTP
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 基础信息齐全,可以先按官方文档接入试跑。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zyla Labs MCP (84f50b)当前 未标注 HTTP · 远程 远程部署 无 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

14.6 KB
来自项目仓库与上游目录的原文,未做删改

Zyla API Hub MCP Server

An MCP (Model Context Protocol) server that gives any AI agent the ability to call any API on the Zyla API Hub — with a single tool.

Zyla API Hub • Browse APIs • Get an API Key)

You connect this server to your AI agent (Claude, Cursor, OpenClaw, OpenAI Agents, etc.), and the agent automatically learns how to make HTTP requests to any Zyla API endpoint. No custom code needed.

Built with the official MCP Python SDK (v1.x).


Table of Contents

  • How It Works (Simple Explanation)
  • Quick Start (3 Steps)
  • Connecting to AI Agents
  • Claude Desktop
  • Claude Code (CLI)
  • Cursor IDE
  • OpenClaw
  • OpenAI Agents SDK
  • LangChain
  • Custom Python Agent
  • SSE Network Agent
  • MCP Inspector (Testing)
  • What the Agent Sees
  • Usage Examples
  • Docker Deployment
  • Project Structure
  • Troubleshooting
  • License

How It Works (Simple Explanation)```

You (human) AI Agent This MCP Server Zyla API Hub
│ │ │ │
│ "Get crime data │ │ │
│ for zip 90210" │ │ │
│ ──────────────────► │ │ │
│ │ call_api(GET, url, │ │
│ │ headers, params) │ │
│ │ ─────────────────────► │ HTTP GET │
│ │ │ ─────────────────────► │
│ │ │ JSON response │
│ │ │ ◄───────────────────── │
│ │ {status: 200, │ │
│ │ response: {...}} │ │
│ │ ◄───────────────────── │ │
│ "Crime grade is │ │ │
│ B+ for 90210..." │ │ │
│ ◄────────────────── │ │ │


**In plain words:**

1. You ask your AI agent a question (in natural language).
2. The agent decides it needs to call an API and uses the `call_api` tool from this server.
3. This server makes the HTTP request to the Zyla API Hub and returns the data.
4. The agent reads the data and answers you in natural language.

The agent figures out **which API to call, what parameters to use, and how to interpret the results** — all on its own. You just ask the question.

---

## Quick Start (3 Steps)

### 1. Install```bash
git clone https://github.com/zyla-labs/zyla-api-hub-mcp.git
cd zyla-api-hub-mcp
pip install -r requirements.txt

2. Run```bash

python mcp_server.py


### 3. Connect your AI agent

Pick your agent from the list below and follow the one-time setup. After that, just chat normally — the agent will use the Zyla APIs when needed.

---

## Connecting to AI Agents

### Claude Desktop

Add to your config file (`claude_desktop_config.json`):

| OS      | Path                                                           |
|---------|----------------------------------------------------------------|
| macOS   | `~/Library/Application Support/Claude/claude_desktop_config.json` |
| Windows | `%APPDATA%\Claude\claude_desktop_config.json`                  |
| Linux   | `~/.config/Claude/claude_desktop_config.json`                  |
```json
{
  "mcpServers": {
    "zyla-api-hub": {
      "command": "python",
      "args": ["/absolute/path/to/mcp_server.py"],
      "env": {}
    }
  }
}

Restart Claude Desktop. You'll see a hammer icon in the chat — that means the tool is available. Just ask:

> "Use the Zyla API to get the crime rates for zip code 90210. My API key is Bearer sk-zyla..."


Claude Code (CLI)```bash

claude mcp add zyla-api-hub -- python /absolute/path/to/mcp_server.py


Then chat normally. Claude Code will invoke `call_api` when it needs to call an API.

---

### Cursor IDE

Add to `.cursor/mcp.json` in your project (or global Cursor settings):```json
{
  "mcpServers": {
    "zyla-api-hub": {
      "command": "python",
      "args": ["/absolute/path/to/mcp_server.py"]
    }
  }
}

In Cursor's Agent mode, the AI will use call_api when you ask it to fetch data from an API.


OpenClaw

OpenClaw is a self-hosted AI agent gateway that supports multiple chat channels (WhatsApp, Telegram, Slack, Discord, iMessage, etc.) and can use external tools via MCP.

Option A — Add via CLI (recommended):```bash
openclaw mcp add --transport stdio zyla-api-hub python /absolute/path/to/mcp_server.py


This registers the MCP server so the OpenClaw agent can discover and use the `call_api` tool.

**Option B — Add via config (`~/.openclaw/openclaw.json`):**

If you prefer manual configuration, add the MCP server in your OpenClaw config:```json5
{
  // ... your existing openclaw.json config ...
  "mcpServers": {
    "zyla-api-hub": {
      "command": "python",
      "args": ["/absolute/path/to/mcp_server.py"],
      "transport": "stdio"
    }
  }
}

Then restart the gateway:```bash
openclaw gateway restart


**Option C — Docker + SSE (network deployment):**

If your OpenClaw gateway runs on a remote server or in Docker, use SSE transport:```bash
# Start the MCP server with SSE transport
docker run -p 8000:8000 -e MCP_TRANSPORT=sse ghcr.io/zyla-labs/mcp-server:latest

# Then register it in OpenClaw pointing to the network URL
openclaw mcp add --transport sse zyla-api-hub http://localhost:8000/sse

Using it:

Once connected, chat with your OpenClaw agent through any channel (WhatsApp, Slack, Telegram, etc.) and it will automatically use the Zyla API when needed:```
You (via WhatsApp): "What's the weather like in Buenos Aires?"

OpenClaw agent → calls call_api(
method="GET",
url="https://www.zylalabs.com/api/.../weather",
headers={"Authorization": "Bearer sk-zyla..."},
params={"city": "Buenos Aires"}
)

OpenClaw agent: "It's currently 18C and partly cloudy in Buenos Aires."


For more on OpenClaw setup, see the Getting Started guide.

---

### OpenAI Agents SDK

The OpenAI Agents SDK supports MCP servers as tool providers natively:```python
from agents import Agent
from agents.mcp import MCPServerStdio

async with MCPServerStdio(
    command="python",
    args=["/absolute/path/to/mcp_server.py"],
) as mcp_server:
    agent = Agent(
        name="Zyla Assistant",
        instructions="You can call any API on the Zyla API Hub using the call_api tool.",
        mcp_servers=[mcp_server],
    )
    # The agent now has access to call_api

LangChain

Use the LangChain MCP Adapter to wrap MCP tools as LangChain tools:```python
from langchain_mcp_adapters.client import MultiServerMCPClient

async with MultiServerMCPClient({
"zyla-api-hub": {
"command": "python",
"args": ["/absolute/path/to/mcp_server.py"],
"transport": "stdio",
}
}) as client:
tools = client.get_tools()
# Use tools with any LangChain agent


---

### Custom Python Agent

Build your own agent using the official MCP Python SDK:```python
import asyncio
from mcp import ClientSession, StdioServerParameters
from mcp.client.stdio import stdio_client

async def main():
    # 1. Point to the MCP server
    server_params = StdioServerParameters(
        command="python",
        args=["mcp_server.py"],
    )

    # 2. Connect
    async with stdio_client(server_params) as (read, write):
        async with ClientSession(read, write) as session:
            await session.initialize()

            # 3. See available tools
            tools = await session.list_tools()
            print("Tools:", [t.name for t in tools.tools])
            # Output: Tools: ['call_api']

            # 4. Call an API
            result = await session.call_tool("call_api", arguments={
                "method": "GET",
                "url": "https://www.zylalabs.com/api/824/crime+data+by+zipcode+api/583/get+crime+rates+by+zip",
                "headers": {"Authorization": "Bearer YOUR_ZYLA_API_KEY"},
                "params": {"zip": "90210"},
            })

            # 5. Read the response
            print("Status:", result.structured_content["status_code"])
            print("Data:", result.structured_content["response"])

asyncio.run(main())

SSE Network Agent

For agents connecting over HTTP (web apps, microservices, remote deployments):```bash

Start the server with SSE transport first

python mcp_server.py sse
``````python
import asyncio
from mcp import ClientSession
from mcp.client.sse import sse_client

async def main():
async with sse_client("http://localhost:8000/sse") as (read, write):
async with ClientSession(read, write) as session:
await session.initialize()

        result = await session.call_tool("call_api", arguments={
            "method": "GET",
            "url": "https://www.zylalabs.com/api/XXXX/your+api/YYY/endpoint",
            "headers": {"Authorization": "Bearer YOUR_KEY"},
        })
        print(result.structured_content)

asyncio.run(main())


---

### MCP Inspector (Testing)

The MCP Inspector lets you test the server interactively in a browser:```bash
# Terminal 1: start the server
python mcp_server.py sse

# Terminal 2: start the inspector
npx -y @modelcontextprotocol/inspector

Open the Inspector UI and connect to http://localhost:8000/sse. You can browse the tool schema and invoke call_api manually.


What the Agent Sees

When an AI agent connects, it receives this tool schema automatically via the MCP protocol:

Tool name: call_api

Description (read by the LLM):
> Call any API endpoint from the Zyla API Hub. Supports GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS. Always include an Authorization header with your Zyla API key.

Input parameters:

Parameter Type Required What it does
method string Yes HTTP method (GET, POST, PUT, DELETE, PATCH, etc.)
url string Yes Full API endpoint URL
headers dict[str, str] No HTTP headers (include Authorization here)
params dict[str, str] No Query-string parameters (sent on all methods)
data dict No JSON body (for POST, PUT, PATCH only)

Output (structured):

Field · Type · What it means
status_code · int · HTTP status code (200, 404, etc.). 0 = request didn't reach the server
response · str \ · dict \ · list · Parsed JSON body, or raw text if not JSON
error · str \ · null · Error message if something went wrong; null on success


Usage Examples

Simple GET```json

{
"method": "GET",
"url": "https://www.zylalabs.com/api/824/crime+data+by+zipcode+api/583/get+crime+rates+by+zip",
"headers": { "Authorization": "Bearer YOUR_ZYLA_API_KEY" },
"params": { "zip": "90210" }
}


### POST with JSON body```json
{
  "method": "POST",
  "url": "https://www.zylalabs.com/api/XXXX/some+api/YYY/endpoint",
  "headers": {
    "Authorization": "Bearer YOUR_ZYLA_API_KEY",
    "Content-Type": "application/json"
  },
  "data": { "input_text": "Hello, world!", "language": "en" }
}

POST with query params + body```json

{
"method": "POST",
"url": "https://www.zylalabs.com/api/XXXX/some+api/YYY/search",
"headers": { "Authorization": "Bearer YOUR_ZYLA_API_KEY" },
"params": { "page": "1", "limit": "10" },
"data": { "query": "machine learning" }
}


### Success response```json
{
  "status_code": 200,
  "response": { "data": "...", "count": 42 },
  "error": null
}

Error response```json

{
"status_code": 0,
"response": "",
"error": "Request timed out after 30 seconds"
}


---

## Docker Deployment

### Build```bash
docker build -t zyla-mcp-server .

Run (stdio — for local agents)```bash

docker run -i zyla-mcp-server


### Run (SSE — for network agents)```bash
docker run -p 8000:8000 -e MCP_TRANSPORT=sse zyla-mcp-server

Pre-built image```bash

docker pull ghcr.io/zyla-labs/mcp-server:latest
docker run -p 8000:8000 -e MCP_TRANSPORT=sse ghcr.io/zyla-labs/mcp-server:latest


The CI pipeline auto-publishes to GitHub Container Registry on every push to `master`.

---

## Project Structure```
zyla-api-hub-mcp/
├── mcp_server.py          # MCP server (single file, all logic)
├── pyproject.toml          # Python packaging (PEP 621)
├── requirements.txt        # Pinned dependencies
├── Dockerfile              # Docker image
├── .dockerignore
├── .github/
│   └── workflows/
│       └── publish.yml     # CI/CD → GHCR
└── README.md

Dependencies: mcp[cli]>=1.26.0, httpx>=0.27.0 — that's it.

Key design choices:
- Official mcp SDK (mcp.server.fastmcp.FastMCP), not the third-party fastmcp package
- httpx instead of requests (async-ready, aligned with the MCP ecosystem)
- Pydantic ApiResponse model for structured output (LLMs get a typed JSON schema)
- No mutable default arguments (None instead of {})
- Granular error handling (timeout, request error, unexpected error — each with a clear message)
- Query params sent on all HTTP methods (not just GET)
- Transport selectable via CLI argument (stdio or sse)


Troubleshooting

Problem Solution
ModuleNotFoundError: No module named 'mcp' Run pip install -r requirements.txt
Server starts but agent can't see the tool Make sure you're using the right transport. Local agents (Claude Desktop, Cursor) use stdio (default). Network agents use sse.
Request timeout errors The default timeout is 30 seconds. If the upstream Zyla API is slow, you'll get a clear error message.
Docker SSE "connection refused" Expose the port: docker run -p 8000:8000 -e MCP_TRANSPORT=sse zyla-mcp-server
OpenClaw doesn't see the tool Restart the gateway after adding the MCP server: openclaw gateway restart

License

MIT

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Zyla Labs MCP (84f50b) 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Zyla Labs MCP (84f50b) 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Zyla Labs MCP (84f50b) 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zyla Labs MCP (84f50b) 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Zyla Labs MCP (84f50b) 能提供哪些能力?

资料显示能力标签包括 安全认证、OAuth认证、HTTP。具体工具清单以官方文档为准。

Zyla Labs MCP (84f50b) 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Zyla Labs MCP (84f50b) 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。