MCP server
Connect an AI tool to your Gripz workspace over the Model Context Protocol. Access uses OAuth 2.1, so the tool only gets the scopes a person approved, and every call is written to the audit log.
What the server exposes
Read tools for conversations, contacts, companies, tickets, help center articles and macros. Two write tools: add an internal note, and create a draft reply. A draft is never sent until a teammate reviews it.
Connect an AI tool
1. Add the server for your region to the tool's MCP settings. Step-by-step pages cover Claude, ChatGPT and Cursor.
{ "mcpServers": { "gripz": { "type": "http", "url": "https://mcp.eu.gripz.example/v1" } } }2. Start the tool. Your browser opens a Gripz consent screen where you pick the workspace and the scopes. An admin can limit which scopes may be granted.
3. Check the connection with a read-only question, for example "Find open conversations about refunds from this week".
Tools and scopes
| Tool | What it does | Scope | Access |
|---|---|---|---|
| search_conversations | Search by text, state, tag or date | conversations:read | Read |
| get_conversation | One conversation with every message | conversations:read | Read |
| search_contacts | Find people and companies | contacts:read | Read |
| get_ticket | A ticket with its state and history | tickets:read | Read |
| search_articles | Search published help center articles | articles:read | Read |
| add_internal_note | Adds a note that only your team sees | notes:write | Write |
| create_draft_reply | Saves a draft for review. Never sends | drafts:write | Write |
There is no tool that sends a message to a customer, closes a conversation or deletes data. MCP calls count against your API rate limit, with a separate share for each AI client.