Graviola: Connect your AI

Choose a connection

MCP lets your assistant use Graviola tools. OAuth connects your Graviola account in the browser without pasting a key into chat. The API is for applications and clients with a private credential setting.

https://mcp.graviola.dev/api/mcp

Claude web and mobile

In Claude web, open Customize or Settings, then Connectors. The exact menu depends on your client and workspace.
Add a custom connector named Graviola with the MCP URL above.
Sign in to Graviola, choose the correct workspace, access and expiry, and complete consent.
Enable the connector in your conversation. On mobile, use the same Claude account and confirm the connector is available. Client plan and workspace policies may affect support.
Ask for a read only connection check before running a search.

Claude Code

Run the command in a terminal. Open /mcp inside Claude Code and complete the Graviola sign in flow.

claude mcp add --transport http graviola https://mcp.graviola.dev/api/mcp

Claude Code reference ↗

Codex

Use an existing Graviola plugin if your Codex client offers it. Otherwise, add the remote server with the CLI and sign in. Keep the terminal open until the local callback finishes.

codex mcp add graviola --url https://mcp.graviola.dev/api/mcp
codex mcp login graviola
codex mcp list

Official OpenAI documentation ↗

OpenCode

Add the remote server and complete OAuth. If your installed version uses a wizard, run opencode mcp add and follow its prompts instead.

opencode mcp add graviola --url https://mcp.graviola.dev/api/mcp
opencode mcp auth graviola
opencode mcp list

ChatGPT

Use the Graviola plugin or app offered by your ChatGPT account and complete its Graviola account connection. Keep the app enabled for the conversation. Custom MCP connection options depend on the client, plan and workspace policy.

If custom remote MCP setup is available, use the same Graviola MCP URL and complete OAuth. If it is not offered, use an available supported plugin or another compatible client. Pasting an API key into chat does not create a connection.

OpenAI authentication reference ↗

Cursor and other MCP clients

Open the client’s MCP or tools settings and add a remote HTTP server.
Name it Graviola and use https://mcp.graviola.dev/api/mcp.
Complete OAuth if offered, choosing the intended workspace and access.
Enable the connection in the conversation and run the read only check below.
Use a key only when the client provides a private Bearer credential setting. A model API without a tool runtime cannot execute Graviola requests on its own.

Cursor MCP reference ↗

Choose access deliberately

Full access can allow direct execution without a review for each ordinary data action. It does not remove plan limits, mailbox permissions or the specific review required for deletion, billing and security changes. A connection belongs to the workspace you selected.

Access	Use it for
Read only	View records, workspace information and usage.
Read & write	Read data and maintain saved records or drafts.
Full access	Requested searches, enrichment, reveals and authorized workflows within the granted scopes and plan limits.
Custom	Only the scopes selected during consent.

Verify without spending credits

A successful check returns the correct workspace and permissions. A Connected label alone does not prove protected tool calls work. Seeing a localhost callback during CLI login is normal: it returns the browser authorization to the client running on your computer.

Check my Graviola workspace, access and remaining allowances using only workspace_status and usage_get. Do not search, enrich, reveal contacts or send anything.

OpenCode reference ↗Troubleshoot a connection ↗Use an API key ↗