Overview
The Tirver MCP server lets an AI assistant such as Claude read and act on your workspace: search articles, read conversations, draft replies and file feedback. MCP, the Model Context Protocol, is the open standard that assistants use to connect to tools.
It is separate from the REST API, which is for your own code. Use MCP when a person works through an assistant. Use the API when a program works on its own. Both use the same API key, and they share its rate limit.
What an assistant can do
| Job | Tool |
|---|---|
| Find an answer in your help center | search_articles |
| See what is waiting in the inbox | list_conversations |
| Read a conversation and its messages | get_conversation |
| Look up a customer | list_customers |
| Ask the AI agent a question | ask |
| Leave a suggested reply for a teammate | draft_reply |
| File an idea a customer raised | create_feedback_post |
| Start a help article | create_article_draft |
There are 16 tools in all. The full list, with inputs and the scope each needs, is on the tools page.
Safe by design
- A key can only use the tools its scopes allow. The assistant is only shown those tools.
- The write tools never message a customer and never publish anything.
draft_replysaves an internal note for a teammate to read and send.create_article_draftmakes a draft.create_feedback_postfiles a post. - A key works for one workspace only, and you can revoke it at any time.
See permissions for details.
Where it lives
The server speaks MCP Streamable HTTP at one address, and answers POST requests with JSON.
https://app.tirver.com/mcp
Get started
- Connect an assistant in a few minutes.
- Read about permissions and choose what to allow.
- Try the guides: draft replies from your editor and triage feedback with an assistant.