How to use Genaya from any MCP client (Cursor, Windsurf, VS Code, Zed, Gemini CLI)

Add Genayalink

1. 1
   Add an MCP server

   In your client, add an MCP server of the HTTP (remote) kind. Name it Genaya and paste the address https://api.genaya.com/mcp. The exact menu differs by client - MCP settings in an editor, an mcp add command in a terminal tool, or a JSON config file with a url field; the host-by-host list below has each one.

2. 2
   Sign in and allow

   The client opens the Genaya consent screen in your browser. It shows the app as an unverified app with its address in bold - that is expected for a client Genaya has not named - or as the client your administrator created, "(set up by your organization)". Sign in with your normal Genaya login (two-factor and login verification apply), pick your organization, tick Prepare changes you confirm if you want the assistant to prepare changes, and tap Allow.

3. 3
   Ask

   Back in the client, ask "How many appointments do I have this week?". The first answer proves the connection; from then on just ask - or ask for a change and confirm it.

The same rules as every assistantlink

• Every change is confirmed by you. A record change - a task, client, lead, reminder, appointment, estimate or invoice draft, expense, a reschedule, cancel or complete - is previewed and confirmed in the chat and can be undone for 15 minutes from any surface; every text, email, invoice or estimate link, anything at or over $2,500, more than 25 recipients, a changed contact detail, a change with no undo or wording that came from customer text is confirmed on a Genaya page where you are signed in. Money, billing, roles, phone numbers and automations are never available.
• One question is 10 Genaya AI credits, a message that prepares a change is 20, exactly like the app; confirm, cancel and undo are free. There is no separate meter and nothing is charged per lookup - a question or an action through any client spends the same Genaya AI credits as in the app and nothing else.
• Your permissions, one organization. The client sees only what your role can see, in the organization you picked. A role change lands within a minute; a revoke lands on the very next call.
• Revoke any time under Settings > Integrations > Use Genaya from ChatGPT and Claude. The connection is listed as Other with the app's name and address, and it expires on its own after 30 days without use.
• Everything is on the record: every question as a conversation in your Genaya AI history, marked Other, and every change as a row in Settings > Genaya AI > Activity with its preview, its receipt and Undo while the window is open.

Host by hostlink

The same steps are printed on the connect page in Genaya (Settings > Integrations > Use Genaya from ChatGPT and Claude) and on the phone, from one list. Where a host has a directory, its status is stated as it is today. Hosts that sign in with a client id and secret are covered in "Create a client for an assistant"; hosts that take an API key in "Use Genaya from a developer tool with an API key".

ChatGPTlink

Chat assistant. Sign-in: a published identity Genaya already recognizes - the consent screen names it.

1. In ChatGPT open Settings and turn on developer mode under Plugins.
2. Choose add a plugin and paste the Genaya address.
3. Sign in with Genaya and pick the organization to connect.
4. Ask ChatGPT a question about your schedule to confirm it works.

Plus, Pro, Business, Enterprise and Edu accounts on the web. Streamable HTTP only. Business and Enterprise admins can allow the plugin company-wide. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. Genaya is submitted to the ChatGPT Plugins Directory; until it is listed there, the address is the way in.

Claudelink

Chat assistant. Sign-in: a published identity Genaya already recognizes - the consent screen names it.

1. In Claude open Settings, then Connectors, then Add custom connector.
2. Paste the Genaya address and save.
3. Choose Connect, sign in with Genaya and pick the organization.
4. Ask Claude a question about your day to confirm it works.

Free accounts get one custom connector. On Team and Enterprise an owner adds it once and members connect individually. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. Genaya is submitted to the Claude Connectors Directory; until it is listed there, the address is the way in.

Claude Codelink

Developer tool. Sign-in: a published identity Genaya already recognizes - the consent screen names it.

1. In a Claude Code session run the two plugin lines, in order.
2. Sign in with Genaya in the browser tab that opens and pick the organization.
3. Ask Claude Code a question about your schedule to confirm it works.

The plugin adds the server and the starter skills. The one-line add command is the alternative. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. Genaya is submitted to the Claude Code plugin marketplace; until it is listed there, the address is the way in.

Copilot Studiolink

Enterprise assistant. Sign-in: the host registers itself and opens the Genaya consent screen, or a client id and secret an administrator creates under Details.

1. In Copilot Studio open Tools, choose Add a tool, then New tool, then Model Context Protocol.
2. Enter Genaya, a short description and the Genaya address.
3. Pick Dynamic discovery to sign in with Genaya, or paste a client id and secret an administrator created under Details.
4. Publish the agent and ask it a question about your schedule.

Streamable HTTP only. An admin creates the client under Details for manual mode. The API key mode takes an API key with Allow MCP. Governed by Power Platform data policies. The host does not document a confirmation prompt on write tools - verify before relying on it; Genaya confirms every change itself regardless, in the chat or on a Genaya page. A listing on the Agent 365 tool registry is a later step; today the address is the way in.

Cursorlink

Developer tool. Sign-in: the host registers itself and opens the Genaya consent screen, or an API key with Allow MCP as the bearer (read and ask only).

1. In Cursor open Settings, then MCP, and add a server with the Genaya address, or use the Add to Cursor link on the developer docs.
2. Sign in with Genaya in the browser tab that opens and pick the organization.
3. Ask a question about your schedule in a chat to confirm it works.

Self-registration by default. An API key with Allow MCP as a header also works. Enterprise admins allowlist servers. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. A listing on the Cursor Marketplace is a later step; today the address is the way in.

Gemini APIlink

Developer tool. Sign-in: an API key with Allow MCP as the bearer (read and ask only; see "Use Genaya from a developer tool with an API key").

1. Create an API key with Allow MCP under Settings, then Developer in Genaya.
2. List Genaya as a remote tool server in your request with the Genaya address and an Authorization header carrying the key.
3. Call whoami first; the key answers questions and reads only.

An API key with Allow MCP, read and ask only. Streamable HTTP only. A live key needs a paid plan; the trial uses a test key. Model usage is billed by the Gemini API account. The host does not document a confirmation prompt on write tools - verify before relying on it; Genaya confirms every change itself regardless, in the chat or on a Genaya page. Gemini API has no directory for custom servers: Genaya is added by address.

Gemini applink

Chat assistant. Sign-in: the host registers itself and opens the Genaya consent screen.

1. In the Gemini app open Settings and help, then Connected apps, then Custom apps for Spark.
2. Choose Add a custom app and paste the Genaya address.
3. Sign in with Genaya and pick the organization to connect.
4. Ask a question about your schedule in Spark to confirm it works.

Available as a custom app in Spark on personal accounts in the US. AI Pro and AI Ultra plans. Manual client credentials work when self-registration is off. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. Gemini app has no directory for custom servers: Genaya is added by address.

Gemini CLIlink

Developer tool. Sign-in: the host registers itself and opens the Genaya consent screen, or an API key with Allow MCP as the bearer (read and ask only).

1. Add a Genaya entry to the mcpServers section of your Gemini CLI settings with the Genaya address as httpUrl.
2. Start Gemini CLI and sign in with Genaya in the browser tab that opens.
3. Ask a question about your schedule to confirm it works.

Self-registration by default. An API key with Allow MCP as a header also works. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. Gemini CLI has no directory for custom servers: Genaya is added by address.

Gemini Enterpriselink

Enterprise assistant. Sign-in: a client id and secret an administrator creates under Details (see "Create a client for an assistant").

1. Ask a Genaya administrator to create a client for Gemini Enterprise under Details on this page and give you the client id and secret.
2. In Gemini Enterprise add a Custom MCP server connection with the Genaya address, the client id and the secret.
3. Turn PKCE on and save the connection.
4. Members sign in with Genaya the first time they use it.

An admin creates the client under Details. Streamable HTTP only. Workspace admins add it; members cannot self-add. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. Gemini Enterprise has no directory for custom servers: Genaya is added by address.

Groklink

Chat assistant. Sign-in: the host registers itself and opens the Genaya consent screen, or an API key with Allow MCP as the bearer (read and ask only).

1. Open grok.com/connectors, choose New Connector, then Custom.
2. Paste the Genaya address and sign in with Genaya.
3. Ask Grok a question about your schedule to confirm it works.

Offered on SuperGrok plans. The Grok API developer path takes an API key with Allow MCP. The host does not document a confirmation prompt on write tools - verify before relying on it; Genaya confirms every change itself regardless, in the chat or on a Genaya page. There is no submission path to the Grok connectors catalog, so Genaya is added by address.

Microsoft 365 Copilotlink

Enterprise assistant. Sign-in: the host registers itself and opens the Genaya consent screen, or a client id and secret an administrator creates under Details.

1. In the Agents Toolkit add an action to your declarative agent and start with an MCP server using the Genaya address.
2. Pick sign-in with Genaya, or paste a client id and secret an administrator created under Details.
3. Sideload the agent, then publish it to your organization catalog.
4. Ask the agent a question about your schedule to confirm it works.

An admin creates the client under Details for static registration. The tenant must allow custom app upload. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. A listing on the Microsoft Commercial Marketplace is a later step; today the address is the way in.

Makelink

Automation platform. Sign-in: the host registers itself and opens the Genaya consent screen, or an API key with Allow MCP as the bearer (read and ask only).

1. In Make add the MCP Client module to a scenario.
2. Paste the Genaya address and sign in with Genaya, or use an API key with Allow MCP as the token.
3. Pick a tool in the module and run the scenario.

Paid plans. An API key with Allow MCP as the token. The host does not document a confirmation prompt on write tools - verify before relying on it; Genaya confirms every change itself regardless, in the chat or on a Genaya page. Make has no directory for custom servers: Genaya is added by address.

Notionlink

Workspace agent. Sign-in: the host registers itself and opens the Genaya consent screen, or an API key with Allow MCP as the bearer (read and ask only).

1. Ask a Notion workspace admin to enable custom MCP servers under Settings, then Connections.
2. Open a custom agent, add a connection with the Genaya address and sign in with Genaya.
3. Ask the agent a question about your schedule to confirm it works.

Business and Enterprise plans. A workspace admin enables custom servers first. Each connection is bound to one agent. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. There is no submission path to the Notion pre-configured servers, so Genaya is added by address.

Perplexitylink

Chat assistant. Sign-in: the host registers itself and opens the Genaya consent screen, or an API key with Allow MCP as the bearer (read and ask only).

1. In Perplexity open Settings, then Connectors, then Custom connector, then Remote.
2. Paste the Genaya address and sign in with Genaya.
3. Ask a question about your schedule to confirm it works.

Pro, Max and Enterprise plans. The host does not document a confirmation prompt on write tools - verify before relying on it; Genaya confirms every change itself regardless, in the chat or on a Genaya page. There is no submission path to the Perplexity connector catalog, so Genaya is added by address.

Salesforce Agentforcelink

Workspace agent. Sign-in: a client id and secret an administrator creates under Details (see "Create a client for an assistant").

1. Ask a Genaya administrator to create a client for Salesforce Agentforce under Details on this page.
2. In Setup register Genaya in the Agentforce Registry with the Genaya address and an External Client App using the client id and secret.
3. Allowlist the tools and add them to an agent in Agent Builder.
4. Ask the agent a question about your schedule to confirm it works.

An admin creates the client under Details. OAuth only; no API keys. Each agent can use up to about 20 tools. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. A listing on the AgentExchange is a later step; today the address is the way in.

Slacklink

Workspace agent. Sign-in: the host registers itself and opens the Genaya consent screen, or a client id and secret an administrator creates under Details.

1. Ask a Genaya administrator to create a client for Slack under Details on this page.
2. In your Slack app manifest declare the Genaya address as an MCP server with the mcp:connect scope and the client id and secret.
3. Submit the app to the Slack Marketplace or install it in your workspace.
4. Connect Genaya from Slackbot and ask a question about your schedule.

Only through a published or internal Slack app; a pasted address is not accepted. Streamable HTTP only. An admin creates the client under Details. Read-only tools on by default; writes ask per action. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. A listing on the Slack Marketplace is a later step; today the address is the way in.

VS Codelink

Developer tool. Sign-in: the host registers itself and opens the Genaya consent screen, or an API key with Allow MCP as the bearer (read and ask only).

1. In VS Code run MCP: Add Server, choose HTTP and paste the Genaya address.
2. Sign in with Genaya when VS Code asks and pick the organization.
3. Ask a question about your schedule in a chat to confirm it works.

Self-registration first, then a client an admin creates under Details. An API key with Allow MCP as a header also works. The org policy for Copilot Business and Enterprise may restrict servers. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. A listing on the GitHub MCP Registry is a later step; today the address is the way in.

Windsurflink

Developer tool. Sign-in: the host registers itself and opens the Genaya consent screen, or an API key with Allow MCP as the bearer (read and ask only).

1. In Windsurf open the MCP settings and add a server with the Genaya address.
2. Sign in with Genaya in the browser tab that opens and pick the organization.
3. Ask a question about your schedule to confirm it works.

Self-registration by default. An API key with Allow MCP as a header also works. Team admins can allowlist servers. The host shows its own approve prompt before a write tool runs; Genaya confirms every change itself regardless, in the chat or on a Genaya page. A listing on the Windsurf MCP Marketplace is a later step; today the address is the way in.

Zapierlink

Automation platform. Sign-in: the host registers itself and opens the Genaya consent screen, or an API key with Allow MCP as the bearer (read and ask only).

1. In Zapier open Apps, choose Add connection, then MCP Client.
2. Paste the Genaya address, pick Streamable HTTP and sign in with Genaya, or use an API key with Allow MCP as the bearer token.
3. Use Run Read-Only Tool or Run Tool in a Zap or an agent.

The branded Genaya app on Zapier stays the main road. An API key with Allow MCP as the bearer. Tools only; Run Read-Only Tool for searches. The host does not document a confirmation prompt on write tools - verify before relying on it; Genaya confirms every change itself regardless, in the chat or on a Genaya page. Zapier has no directory for custom servers: Genaya is added by address.

Zedlink

Developer tool. Sign-in: an API key with Allow MCP as the bearer (read and ask only; see "Use Genaya from a developer tool with an API key").

1. Create an API key with Allow MCP under Settings, then Developer in Genaya.
2. In Zed settings add Genaya as a context server with the Genaya address and an Authorization header carrying the key.
3. Ask a question about your schedule to confirm it works.

An API key with Allow MCP, read and ask only. A live key needs a paid plan; the trial uses a test key. The host does not document a confirmation prompt on write tools - verify before relying on it; Genaya confirms every change itself regardless, in the chat or on a Genaya page. Zed has no directory for custom servers: Genaya is added by address.