Use Genaya from a developer tool with an API key (Cursor, VS Code, Windsurf, Zed, Gemini CLI, the Gemini and Grok APIs, Zapier, Make)

• Two tools: who am I and ask Genaya AI (scopes read and ai). Prepare a change, confirm, cancel, undo and list changes answer that the key cannot use them - no confirm page, no in-chat confirmation, ever.
• As the member who created the key. Their permissions, their company scope, their organization. If that member loses access the key stops: "The member who created this key no longer has access - create a new key."
• Test keys work (gny_test_), flagged as test mode; they read live data like a test key on the Developer API does.
• The organization's External assistants switch and Allowed assistants do not apply to a key - the Developer API switch, the plan and the creator's Genaya AI permissions do.
• The key's own limits. A call spends the connector windows keyed on the key (60 a minute, 5,000 a day) and nothing on the key's Developer API request pool. A question to Genaya AI costs 10 Genaya AI credits, exactly like the app - the same credits, and nothing else. Who am I is free.
• On the record. Every call is logged as an API-key call with the key's public prefix, the key row shows its last MCP call, and every question is a conversation in the creator's Genaya AI history, marked Other.

Configuration by toollink

Each entry is the whole configuration on one line; replace gny_live_... with your key. Cursor, VS Code, Windsurf and Gemini CLI can also sign in with Genaya instead (leave the header out), which makes the connection personal and lets it prepare changes you confirm.

Cursor (~/.cursor/mcp.json)

{ "mcpServers": { "genaya": { "url": "https://api.genaya.com/mcp", "headers": { "Authorization": "Bearer gny_live_..." } } } }

VS Code (.vscode/mcp.json)

{ "servers": { "genaya": { "type": "http", "url": "https://api.genaya.com/mcp", "headers": { "Authorization": "Bearer ${input:genaya-key}" } } }, "inputs": [{ "id": "genaya-key", "type": "promptString", "password": true, "description": "Genaya API key" }] } - VS Code prompts for the key once and keeps it in its secret store.

Windsurf (mcp_config.json)

{ "mcpServers": { "genaya": { "serverUrl": "https://api.genaya.com/mcp", "headers": { "Authorization": "Bearer gny_live_..." } } } }

Zed (settings.json)

{ "context_servers": { "genaya": { "source": "custom", "url": "https://api.genaya.com/mcp", "headers": { "Authorization": "Bearer gny_live_..." } } } }

Gemini CLI (~/.gemini/settings.json)

{ "mcpServers": { "genaya": { "httpUrl": "https://api.genaya.com/mcp", "headers": { "Authorization": "Bearer gny_live_..." } } } }

Gemini API (in the request, server side)

"tools": [{ "type": "mcp_server", "name": "genaya", "url": "https://api.genaya.com/mcp", "headers": { "Authorization": "Bearer gny_live_..." }, "allowed_tools": ["whoami", "ask_genaya"] }] - the name is snake_case with no hyphens; streamable HTTP only, which Genaya is.

Grok API (in the request, server side)

"tools": [{ "type": "mcp", "server_url": "https://api.genaya.com/mcp", "server_label": "genaya", "authorization": "gny_live_...", "allowed_tools": ["whoami", "ask_genaya"] }]

Zapier MCP Client

Apps > Add connection > MCP Client: the Genaya address, Streamable HTTP, and the key as the bearer token. Use Run Read-Only Tool in a Zap or an agent. The branded Genaya app on Zapier stays the main road for triggers and actions.

Make MCP Client module

Add the module to a scenario with the Genaya address and token authentication carrying the key; pick a tool and run the scenario.

Two doors, one keylink

POST https://api.genaya.com/v1/mcp is the Developer API's own MCP server: typed tools over the REST resources (list appointments, create a client), with the key's scopes and write rules. https://api.genaya.com/mcp with the same key is the connector: who am I and ask Genaya AI - the brain, read and ask only. Calls to /v1/mcp count on the key's Developer API request pool; calls to /mcp count nothing there, and a question spends Genaya AI credits like the app. The two never mix: a connection token from Sign in with Genaya is never accepted on /v1, and a Zapier key is never accepted on either.