Integrations
Connect Nimaya to the services you already run, and it can answer from live data rather than only from your documents — a payment status, an order, an issue tracker.
Open Integrations in the dashboard and pick a service. Every connector below is built on the Model Context Protocol, so anything else that speaks MCP works too — see MCP integration.
Available now
| Service | What Nimaya can do | Credential |
|---|---|---|
| Stripe | Look up payments, subscriptions, invoices, and issue refunds. | Restricted API key |
| Zapier | Reach 8,000+ apps — whichever actions you configure in Zapier become tools. | Zapier MCP token |
| Linear | Read issues, projects, and cycles so support answers match the roadmap. | Personal API key |
| GitHub | Search issues, pull requests, and repository docs. | Personal access token |
| Shopify | Search your catalogue and answer questions about products, policies, and FAQs. | None needed |
| Jira & Confluence | Look up issues, projects, and Confluence pages so answers match what your team is actually working on. | API token |
Setting each one up
Stripe
- In Stripe, open Developers → API keys and create a Restricted key.
- Grant it read access to the resources the assistant should see — payments, customers, subscriptions.
- Paste the key below. Minaya encrypts it and never shows it again.
Zapier
- Go to mcp.zapier.com and create an MCP server.
- Add the actions you want the assistant to use — Gmail, Sheets, Salesforce, anything Zapier supports.
- Open the Connect tab, choose Other, and copy the token. It is shown only once.
Linear
- In Linear, open Settings → Account → Security & Access.
- Create a Personal API key.
- Paste it below. Minaya connects read-only, so nothing in Linear can be changed.
GitHub
- In GitHub, open Settings → Developer settings → Personal access tokens.
- Create a token with read access to the repositories the assistant should see.
- Paste it below.
Shopify
- Enter your store name — the part before .myshopify.com.
- No token is needed: Shopify’s storefront MCP is public, and exposes only catalogue, cart, and policy data.
- Orders and inventory are not available over MCP. Shopify does not offer a merchant admin server.
Jira & Confluence
- Ask your Atlassian org admin to enable API token access: Atlassian Administration → Rovo → Rovo MCP server → Authentication → API token. Without this, the connection is refused.
- Create a token at id.atlassian.com → Security → Create and manage API tokens.
- Enter the email that owns the token, then paste the token itself.
Coming soon
These services require an OAuth sign-in rather than a pasted key, which we are still building:
| Service | Status |
|---|---|
| ClickUp | ClickUp requires an OAuth sign-in — personal API keys are not accepted. We are building that flow. |
| Notion | Notion’s remote server accepts OAuth only. We are building that flow. |
A note on Shopify
Shopify’s MCP server covers your storefront — catalogue search, cart, and shop policies. There is no merchant admin server, so orders, inventory, and customer records are not available over MCP.
This is a Shopify limitation rather than a Nimaya one. Their MCP servers are built for agents selling to shoppers, not for merchants managing a store.
Anything else
Choose Connect a different service to add any remote MCP server, including one you build yourself. The MCP registry lists what is available, and MCP integration covers building your own.