kobra-api-mcp
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@kobra-api-mcpCheck my partner account info"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
kobra-api-mcp
MCP server para que cualquier IA (Grok, Cursor, Claude Desktop, etc.) use la API Kobra de verdad:
Lee el OpenAPI live (no un PDF viejo)
Sabe cómo autenticarse (partner key, bearer, session)
Ejecuta requests HTTP y devuelve status + body
Default: https://stage.api.trykobra.com. Prod solo con KOBRA_ALLOW_PROD=1.
Install
cd kobra-api-mcp
uv sync
# o: pip install -e .Related MCP server: rest_api_mcp
Run (stdio MCP)
export KOBRA_ENV=stage
export KOBRA_PARTNER_KEY='kbr_…' # para /api/partner/v1/*
uv run python -m kobra_api_mcpConfig para Grok / Cursor / Claude
Ver config/grok-mcp.example.json y config/cursor-mcp.example.json.
Ejemplo Cursor (~/.cursor/mcp.json o settings MCP):
{
"mcpServers": {
"kobra-api": {
"command": "uv",
"args": ["run", "--directory", "/ABS/PATH/kobra-api-mcp", "python", "-m", "kobra_api_mcp"],
"env": {
"KOBRA_ENV": "stage",
"KOBRA_ALLOW_PROD": "0",
"KOBRA_PARTNER_KEY": "kbr_…"
}
}
}
}Grok (sesiones con MCP): mismo bloque mcpServers en la config de MCP del host que use Grok Build / TUI. La key nunca va en el chat: solo en env del server.
Auth (lo que la IA debe saber)
Perfil | Env | Header | Rutas |
| — | — |
|
|
|
|
|
|
|
| si aplica |
|
|
| team/portal |
| (elige) | según path | default en |
Tools:
auth_profiles— qué está configuradocall_route(..., auth_profile="auto"|"partner"|…)— prueba real
Tools
Tool | Uso |
| base URL, auth flags, links a docs humanas |
| cómo autenticar cada perfil |
| re-baja OpenAPI full + partner |
| filtrar method/tag/q |
| detalle + schema + auth_hint |
| HTTP real |
| health + docs sin auth |
|
|
| plan de pruebas ordenado |
| atajos Scalar/SDK |
Flujo recomendado para la IA
1. api_info()
2. auth_profiles()
3. refresh_openapi()
4. list_routes(q="partner") o suggest_probe_plan(focus="partner")
5. get_route("GET", "/api/partner/v1/me")
6. call_route("GET", "/api/partner/v1/me", auth_profile="partner")
7. call_route writes solo en stage, con body del schemaDocs humanas (mismo backend)
URL | Qué |
| Scalar API completa |
| Scalar Partner |
| SDK Python |
| Schema full |
| Schema partner |
Defaults:
stage:
https://stage.api.trykobra.comprod:
https://api.trykobra.com(+KOBRA_ALLOW_PROD=1)
Tests
uv run pytest -q
KOBRA_MCP_LIVE=1 uv run pytest -q tests/test_client_live_optional.pySeguridad
Secretos solo en env del proceso MCP
Headers sensibles se devuelven redactados al modelo
Prod bloqueado por default
No hay tool para “guardar” keys desde el chat
Licencia
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kobra-IA/kobra-api-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server