Kyma API

com.kymaapiPublished by kymaapi.comOfficial publisherv1.0.3Updated Nov 2, 2026

Live model catalog with prices and measured uptime, rankings, credits and spend, spend-capped chat.

VerifiedStreamable HTTPWeb executableData & Analytics AI & ML

Server details

Identifier: com.kymaapi/kyma
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to kymaapi.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.kymaapi%2Fkyma.svg)](https://sourceweft.com/mcp/com.kymaapi%2Fkyma?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Kyma API's MCP server exposes an LLM gateway's live model catalog, prices, rankings, uptime and your spend, plus a spend-capped chat tool.

What you can do: Browse the model catalog: list models, get one model's details, compare prices, see rankings from real traffic and measured 30-day uptime, and get model recommendations for coding agents.
Estimate and check costs: estimate what a call would cost, search Kyma docs, and run a health check.
Review your account: balance, this connection's cap, spent and remaining, usage by model, single requests and credit ledger entries, plus a billing-page link.
Optionally list your REST API keys masked and set a low-balance email alert.
Send a chat completion through any model, with optional token and cost ceilings, and see the cost and remaining cap in each reply.
When to use it: Useful when you want an assistant to pick a model by price and measured uptime, check your Kyma balance and spend cap, or make occasional billed chat calls through one gateway without pasting an API key into the client.
Requirements: A remote endpoint with OAuth 2.1 sign-in (PKCE, dynamic client registration), or the npm stdio bridge run with npx for stdio-only clients. A Kyma account is required; the bridge can use a Kyma MCP key in KYMA_MCP_KEY instead of browser sign-in. Network access to the hosted endpoint.

Before you install

send_message is the only tool that spends credit; each connection gets a dedicated key capped at $10 per 30 days by default (adjustable $1 to $500), and calls are refused once the cap is reached. Keep the client's confirmation prompt on for send_message and treat model output as untrusted text. The optional KYMA_MCP_KEY is a secret; REST keys are rejected on purpose. Request logs are kept 90 days.

Installation

In SourceWeft

Open Kyma API in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.kymaapi%2Fkyma/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "kyma-api": {
      "type": "http",
      "url": "https://mcp.kymaapi.com/mcp"
    }
  }
}

README

[Kyma API]

Kyma API MCP Server

Kyma API is an LLM API gateway that routes one key to 100+ models and publishes measured uptime per model.
Every model behind one endpoint, with public rankings and a spend cap you set.
https://mcp.kymaapi.com/mcp

[MCP Registry] [npm] [Docs] [License]

Install · Tools · Security and spend · Examples · Troubleshooting · Registries

Kyma API is an LLM gateway: one OpenAI-compatible endpoint (plus an Anthropic-compatible one) in front of open and frontier models, with uptime measured per model from real traffic and scheduled probes. This server gives any MCP client the live catalog, prices, rankings, uptime and your own spend as read tools, and one chat tool that is guarded by a per-connection spend cap.

Hosted, remote, OAuth sign-in. Streamable HTTP with OAuth 2.1, PKCE and dynamic client registration. No API key is pasted into the client.
A dedicated key per connection. Separate from your REST API keys, capped at $10 per 30 days by default (adjustable from $1 to $500 on the approval screen or at kymaapi.com/integrations), revocable at any time.
Read tools never charge. Catalog, pricing, rankings, uptime, credits, spend, your usage and your requests are free to call and auto-approved by most clients.
send_message is priced before it spends. The client must allow it first; max_cost_usd is enforced by deriving a max_tokens that fits the ceiling from the catalog price, so a call above it is refused before anything is sent. Every reply reports what the call cost, what has been spent and the cap.
Measured uptime, not a promise. get_model_uptime returns the 30-day rate per model from kymaapi.com/status. If a route fails mid-request, Kyma retries the same model on another route.
A read-only endpoint for reviewers. https://mcp.kymaapi.com/mcp/readonly accepts the same tokens but keeps only read scopes for the request: no send_message, no set_low_balance_alert, whatever the grant was approved with. Metadata: /.well-known/oauth-protected-resource/mcp/readonly.
Beyond chat. The same Kyma key covers speech-to-text, text-to-speech, embeddings, rerank, image and video through the REST API; list_models shows all of them.

Install

Claude Code

Run /mcp to sign in. This repository is also a Claude Code plugin (.claude-plugin/plugin.json + .mcp.json).

Claude.ai and Claude Desktop

Settings → Connectors → Add custom connector → paste https://mcp.kymaapi.com/mcp → sign in with Kyma.

Cursor

One click: Add to Cursor

Or in .cursor/mcp.json:

VS Code (GitHub Copilot)

One click: Install in VS Code

Or in .vscode/mcp.json:

Codex CLI

Cline

Cline → MCP Servers → Configure MCP Servers:

Cline CLI: cline mcp add kyma https://mcp.kymaapi.com/mcp --transport streamableHttp --yes. Cline asks you to sign in with Kyma on first use.

Gemini CLI

The first tool call opens a browser for OAuth sign-in, handled by Gemini CLI.

Grok

grok.com: Connectors → New Connector → Custom → paste the URL.
Grok Build: this repository is a Claude Code format plugin; Grok Build loads it as-is.

ChatGPT (Developer Mode)

Settings → Connectors (Plus, Pro, Business, Enterprise, Edu) → add the URL → sign in. ChatGPT connections never see get_topup_link.

Any stdio-only client

The bridge runs mcp-remote against the hosted URL, so the tools are exactly the hosted ones. Set KYMA_MCP_KEY=km-… (a Kyma MCP key from kymaapi.com/integrations, not a REST kyma-… key) to skip the browser. Source: bridge/.

Tools

18 tools. 16 appear on a default connection; list_keys and set_low_balance_alert appear when their optional scopes are granted on the approval screen.

Tool	What it does	Scope	Approval
`list_models`	Live model catalog with prices, context window and capabilities	`models.read`	auto, read-only
`get_model`	One model's details	`models.read`	auto, read-only
`list_pricing`	Prices across the catalog	`models.read`	auto, read-only
`list_rankings`	Top models and apps from real traffic	`models.read`	auto, read-only
`get_model_uptime`	Measured 30-day uptime per model	`models.read`	auto, read-only
`recommend_model`	Best model and config for Cline, Cursor, Claude Code and other agents	`models.read`	auto, read-only
`search_docs`	Search Kyma docs	`models.read`	auto, read-only
`ping`	Health check	`models.read`	auto, read-only
`get_credits`	Your balance	`usage.read`	auto, read-only
`get_spend`	This connection's cap, spent, remaining and reset date	`usage.read`	auto, read-only
`get_usage`	Your requests, tokens and cost by model over a window	`usage.read`	auto, read-only
`get_request`	One request by id: model served, tokens, cost, routes tried	`usage.read`	auto, read-only
`estimate_cost`	What a call would cost before you make it	`models.read`	auto, read-only
`get_transactions`	Recent credit ledger entries	`usage.read`	auto, read-only
`get_topup_link`	Balance and the billing page (a link, never a checkout)	`usage.read`	auto, read-only
`list_keys`	Your REST API keys by name, masked	`keys.read` (optional)	auto, read-only
`set_low_balance_alert`	Balance at which Kyma emails you	`billing.alerts` (optional)	asks once
`send_message`	A chat completion through any model; the only tool that spends credit; optional `max_tokens` and `max_cost_usd`	`chat.completions`	asks once; no charge without your Allow

Every send_message reply carries cost, spent_usd and spend_cap_usd, plus structuredContent with the model that served it and the routes tried. get_spend shows what is left before you call it.

Security and spend

What a connection can do: read the catalog, prices, rankings, uptime, your balance and this connection's spend; send chat completions up to its cap; with optional scopes, list your keys masked and set a low-balance alert.
What it can never do: create or delete API keys, change billing or payment methods, buy credits, register accounts, or see provider internals. Those scopes do not exist on this server.
Spend cap: each connection gets a dedicated key with its own cap, $10 per 30 days by default, adjustable from $1 to $500. The cap is enforced on the server; when it is reached send_message returns an error until the window resets or you raise the cap at kymaapi.com/integrations.
Tokens and keys: access tokens live 7 days, refresh tokens 90 days and rotate on use; connection keys are stored hashed (SHA-256) and can be revoked without touching your REST API keys.
Prompt injection: model output that reaches your agent is untrusted text. Keep your client's confirmation prompt on for send_message, and do not let the agent paste keys or balances into other tools.
Data: request logs are kept 90 days for billing reconciliation and abuse handling, then deleted. Kyma does not train on customer data. Privacy: kymaapi.com/privacy.

Skills

Three skills teach an agent how to use the tools well: pick-a-model (compare price, measured uptime and fit), check-spend-and-credits (balance, cap, remaining, reset date), send-a-test-completion (one billed call, only after an explicit Allow). They live in skills/ and install into any agent that reads skills:

Examples

Prompts you can paste once connected:

"Which models under $1 per million output tokens have the best 30-day uptime?"
"Recommend a model and config for Cline, then show its price."
"How much of this connection's budget is left, and when does it reset?"
"Send 'summarize this in one line' to qwen-3.6-plus and tell me what it cost."
"Show the top apps on Kyma rankings this week."

Troubleshooting

Sign-in loops or "connector failed": remove the connection and add it again; the client's stored token may belong to a revoked connection. Check kymaapi.com/integrations for the active list.
send_message says the cap is reached: raise the cap at kymaapi.com/integrations or wait for the 30-day window to reset; get_spend shows the date.
A tool returns 403 insufficient scope: the connection was approved without that optional scope. Reconnect and tick it on the approval screen.
Stdio bridge cannot sign in: set KYMA_MCP_KEY to a Kyma MCP key (km-…) created at kymaapi.com/integrations; REST kyma-… keys are rejected on purpose.
Remote connections drop: some clients need a reconnect after long idle periods; the server itself is stateless.

Registries and marketplaces

Official MCP Registry: com.kymaapi/kyma (server.json in this repo, published with mcp-publisher, namespace verified by DNS on kymaapi.com)
Smithery: kyma-api/kyma
npm stdio bridge: @kyma-api/mcp-server
Gemini CLI extensions gallery: gemini-extension.json and the repo topic gemini-cli-extension
Submitted, pending review: Cursor Marketplace, xAI Grok Build marketplace, Docker MCP Catalog, Cline Marketplace, mcp.so

About Kyma API

Kyma is an LLM API gateway: open and frontier models, one endpoint, pay per token, with automatic failover across providers and per-model measured uptime published at kymaapi.com/models. New accounts start with free credit.

Website: https://kymaapi.com · This server's page: https://kymaapi.com/mcp · Docs: https://docs.kymaapi.com · Status: https://kymaapi.com/status
Support: [email protected] · Abuse: [email protected]
Changelog: CHANGELOG.md · License: MIT

Source: README.md at commit ace8e75

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.3LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts