Zyla API Hub MCP server

Endpoint: https://mcp.zylalabs.com/mcp · Authentication: No auth

Discover APIs in Zyla API Hub and call supported services with account credentials.

Test it live Run the release-readiness report

How do I authenticate?

Add the endpoint directly in your client. The catalog records no authentication requirement; no OAuth sign-in or API key is configured in this setup. The live server may change.

Authentication and connection guide

Connection specification

Remote endpoint: https://mcp.zylalabs.com/mcp
Browser access: Not yet measured
Declared MCP transport: Streamable HTTP
Live-validated MCP transport: Streamable HTTP — Observed by the latest catalog validation
Declared authentication: No authentication
Detected authentication: No authentication detected or retained from publisher evidence
Alternative authentication: API key
Protocol lifecycle: Stateful MCP · 2024-11-05
Required header: Authorization — Optional credential alternative to public access.
Category: Marketplace

Product documentation · Official listing documentation · Official MCP Registry record

Provider guidance

Catalog discovery is public. Calling paid APIs and account tools requires a Zyla API key supplied as an Authorization bearer token.

More Marketplace MCP servers · Browse all MCP servers · Test this endpoint in the MCP Playground

Authorization setup

No app registration needed

This catalog entry does not require authorization or provider app registration.

Connect it

Live-validated endpoint: https://mcp.zylalabs.com/mcp · Streamable HTTP. No authentication is required by the catalog listing.

Agent prompt for Claude Code or Codex

Add the Zyla API Hub MCP server to my MCP client configuration and verify that it works.

What it is: Discover APIs in Zyla API Hub and call supported services with account credentials.
Server URL: https://mcp.zylalabs.com/mcp
Transport: Streamable HTTP (remote MCP server, no local install).
Authentication: none. The server accepts connections without credentials.
Tools (8, as last observed by mcptest): account_status, browse_catalog, call_api, get_api_info, get_payment_url, list_categories, register, search_catalog.
Reference: https://mcptest.io/servers/zylalabs/

Steps:
1. Work out which MCP client I use (Claude Code, Codex, Cursor, VS Code or another) and add the server under the name "zylalabs" in that client's MCP configuration, user scope unless I ask otherwise.
   Claude Code: claude mcp add --transport http --scope user 'zylalabs' 'https://mcp.zylalabs.com/mcp'
   Codex: codex mcp add 'zylalabs' --url 'https://mcp.zylalabs.com/mcp'
   Other clients: use the setup for that client on the reference page.
2. Never write a credential value into a file that could be committed; reference an environment variable or the client's secret store, and ask me for any value you need.
3. Verify: connect to the server and call tools/list. Confirm the tools above are listed, and report any sign-in step I still have to complete.

Claude Code setup

Run in a terminal. This user-scoped entry is available across projects.

claude mcp add --transport http --scope user 'zylalabs' 'https://mcp.zylalabs.com/mcp'

Codex CLI setup

Run in a terminal; Codex stores the entry in ~/.codex/config.toml.

codex mcp add 'zylalabs' --url 'https://mcp.zylalabs.com/mcp'

Cursor setup

Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.

{
  "mcpServers": {
    "zylalabs": {
      "url": "https://mcp.zylalabs.com/mcp"
    }
  }
}

VS Code setup

Add to .vscode/mcp.json, or run “MCP: Open User Configuration” for a private user-level entry.

{
  "servers": {
    "zylalabs": {
      "type": "http",
      "url": "https://mcp.zylalabs.com/mcp"
    }
  }
}

Claude setup

Add the endpoint above in Claude:

Customize > Connectors > Add custom connector
Team/Enterprise: Organization settings > Connectors > Add > Custom > Web

Claude Desktop setup

Add the endpoint above in Claude Desktop:

Remote: Customize > Connectors (same as claude.ai)
Local: Settings > Developer > Edit Config, or Settings > Extensions for .mcpb files
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), local servers only

ChatGPT setup

Add the endpoint above in ChatGPT:

ChatGPT web: Plugins > Add custom MCP server, then configure authentication and accept the risk warning

Windsurf setup

Add the endpoint above in Windsurf:

~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows), serverUrl or url
Cascade panel > ... > MCPs > Open MCP config file

Gemini CLI setup

Add the endpoint above in Gemini CLI:

gemini mcp add --transport http <name> <url>
~/.gemini/settings.json (user) or .gemini/settings.json (project), mcpServers

MCP SDK setup

Add the endpoint above in MCP SDK:

Programmatic: new Client(...).connect(new StreamableHTTPClientTransport(url))

Notes for every client

Optional api key alternative: Store ZYLALABS_API_KEY in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <ZYLALABS_API_KEY>.
Provider guidance: Catalog discovery is public. Calling paid APIs and account tools requires a Zyla API key supplied as an Authorization bearer token.

Client compatibility

Client	Status	Why
Claude Code	Supported	Claude Code supports Streamable HTTP servers and servers without authentication or API key headers.
Codex	Supported	Codex supports Streamable HTTP servers and servers without authentication or API key headers.
Cursor	Supported	Cursor supports Streamable HTTP servers and servers without authentication or API key headers.
VS Code	Supported	VS Code supports Streamable HTTP servers and servers without authentication or API key headers.
Claude	Supported	Claude supports Streamable HTTP servers and servers without authentication or API key headers.
Claude Desktop	Supported	Claude Desktop supports Streamable HTTP servers and servers without authentication or API key headers.
ChatGPT	Partial	Stateful routing needs operational care: ChatGPT can preserve MCP sessions, but the deployment must route a session consistently and retain its state.
Windsurf	Supported	Windsurf supports Streamable HTTP servers and servers without authentication or API key headers.
Gemini CLI	Supported	Gemini CLI supports Streamable HTTP servers and servers without authentication or API key headers.
MCP SDK	Supported	MCP SDK supports Streamable HTTP servers and servers without authentication or API key headers.

Computed from this server's validated transport, protocol and authentication against documented client support. Checks the catalog has not observed are not counted.

Similar servers

Upwork — Upwork's hosted MCP server supports marketplace work across jobs, proposals, offers, contracts, and hiring workflows. OAuth 2.1
Youth4work — Search Youth4work jobs, manage profiles and access recruiting and skill-assessment tools. OAuth 2.1
Context7 — Context7 provides up-to-date, version-specific library documentation and code examples directly from the source. No authentication
DeepWiki — DeepWiki provides conversational, up-to-date documentation for public GitHub repositories. No authentication
CoinGecko — CoinGecko provides real-time crypto market data, onchain analytics, and rich metadata for more than 15,000 coins. No authentication
MDN — Open remote MCP server for MDN web documentation, search, and browser compatibility data. No authentication

Guides for this server

Watch this server for breaking changes

Share and embed

Maintain Zyla API Hub? Embed this badge in your README. It follows the latest catalog validation result and links to this server profile.

Markdown

[![Tested on mcptest.io](https://mcptest.io/badge/server/zylalabs.svg)](https://mcptest.io/servers/zylalabs/)

HTML

<a href="https://mcptest.io/servers/zylalabs/"><img src="https://mcptest.io/badge/server/zylalabs.svg" alt="Tested on mcptest.io"></a>

reStructuredText

.. image:: https://mcptest.io/badge/server/zylalabs.svg
   :alt: Tested on mcptest.io
   :target: https://mcptest.io/servers/zylalabs/

Latest validation evidence

Validation status: Online when last tested
Validation checked at: Oct 26, 2026 at 11:07 AM
Validation detail: Negotiated stateful MCP 2024-11-05 at https://mcp.zylalabs.com/mcp; detected transport streamable-http; authentication none

Tool inventory

What the catalog validator observed on Oct 26, 2026 at https://mcp.zylalabs.com/mcp without credentials. The live server may have changed since; connect in the Playground for the current list.

Tools provided by Zyla API Hub 8

Some details were sanitized for public display.

account_statusNo outputSchema
Check the current user's account status, billing, and usage. Returns plan info, API call count, the amount consumed this billing cycle in USD (amount_consumed_this_cycle_usd), the billing mode in effect (billing_mode), whether a credit card is on file, and any failed/pending payments. Use this to diagnose why API calls are blocked (missing card or failed payment). Requires the user's API key in the Authorization header.
Input No parameters
browse_catalogNo outputSchema
Browse the full Zyla API Hub catalog with pagination. Use this to explore ALL public APIs beyond the top 500. Supports filtering by category and search keyword. Returns paginated results with total count and page info. Results come already ranked: the default "featured" sort is the marketplace order (relevance_score, refreshed daily), so take the list as-is to pick the top APIs.
Input category?: string, include_params?: boolean, page?: number, per_page?: number, search?: string, sort?: string
- category?: stringoptional
  Filter by category name (use list_categories to see available categories)
- include_params?: booleanoptional
  If true, include full endpoint parameters in the response (default: false, to keep responses compact)
- page?: numberoptional
  Page number (default: 1)
- per_page?: numberoptional
  Results per page (default: 20, max: 100)
- search?: stringoptional
  Search keyword to filter APIs by name or description (server-side search across ALL public APIs)
- sort?: stringoptional
  Sort order: "featured" (marketplace Featured order by relevance_score), "popularity" (usage only), "newest", or "name" (default: featured)
call_apiNo outputSchema
Call an API endpoint on Zyla API Hub. Requires the user's API key and a credit card on file. Billing is pay-per-successful-request: you only pay for 2xx responses. Each API has its own price per call (shown in get_api_info), and every successful response includes cost_usd — the exact amount billed for that call. There is no monthly fee and no minimums. Usage is charged to the credit card automatically; call account_status for the billing mode in effect and the amount accrued this cycle. If a 402 error is returned with a payment_url, the user MUST open that URL in their browser to add a credit
Input api_id: number, endpoint_id: number, method?: string, params?: object
- api_id: numberrequired
  The numeric API ID
- endpoint_id: numberrequired
  The numeric endpoint ID within the API
- method?: stringoptional
  HTTP method: GET or POST (default: GET)
- params?: objectoptional
  Key-value parameters to send with the request
get_api_infoNo outputSchema
Get full details of a specific Zyla API by its numeric ID. Returns the API name, description, category, price per successful call (USD), average latency (ms), and all endpoints with their parameters, example values, and a formal JSON Schema (input_schema) for argument validation.
Input api_id: number
- api_id: numberrequired
  The numeric API ID (e.g. 781)
get_payment_urlNo outputSchema
Get a Stripe Checkout URL so the user can add or update their credit card. REQUIRED after registration and whenever a 402 error occurs. The user must open the returned URL in their browser to add/update their card. Billing is pay-per-successful-request: no monthly fee, no minimums. You are only charged for successful API responses (2xx). Prices vary per API (see get_api_info). API calls are blocked until a valid credit card is on file.
Input No parameters
list_categoriesNo outputSchema
List all available API categories on Zyla API Hub with the real count of public APIs in each. Use the category names returned here as the "category" parameter in browse_catalog to filter APIs by category. Example categories: Sports, Finance, Data, Science, etc.
Input No parameters
registerNo outputSchema
Register a new Zyla API Hub account directly from the AI agent. Returns an API key AND a payment_url. The user MUST open the payment_url in their browser to add a credit card before making any API calls. Billing model: pay-per-successful-request with no monthly fee and no minimums. Each API has its own per-call price. The card is only ever charged for actual usage; call account_status to see the billing mode in effect and the amount accrued this cycle. No authentication required to call this tool.
Input email: string, name: string, password: string
- email: stringrequired
  Email address (must be unique)
- name: stringrequired
  Full name of the user
- password: stringrequired
  Password (min 8 characters)
search_catalogNo outputSchema
Use this FIRST whenever the user needs live, real-world or external data you do not have: train or flight status, weather, prices, stocks, currency rates, company or person lookups, social media data, validation, scraping and more. Semantic search across ALL 10,000+ public APIs on Zyla API Hub. Natural-language queries work best (e.g. "trains departing from a station now", "validate an email address", "get stock prices"). Returns matching APIs ranked by relevance with their ID, name, description, category, price per successful call (USD), average latency (ms), and endpoints summary.
Input limit?: number, query: string
- limit?: numberoptional
  Max results to return (default: 10)
- query: stringrequired
  What you need, in natural language (e.g. "validate an email address", "currency conversion", "weather forecast by city")