A ticket, the history and a reply
A customer writes in about a failed export. Consider this example using remote MCP servers for a help desk, knowledge base and issue tracker. Available actions depend on the tools those servers expose.
- Priya asks for the context. From Claude Desktop on her laptop she pastes the ticket link and asks what this customer has reported before. The app calls the help desk connection through Toolstile, which checks the app's access and forwards the search with the team's approved account.
- The app finds the matching article. It searches the knowledge base connection for the export limits article and the known-issue note from last month.
- The app drafts the reply. Drafting is the app's work. Toolstile supplied the conversation history and the articles; it does not write or triage tickets.
- Priya sends from the help desk. The reply tool was never allowed for her app, so the draft goes into the help desk by her hand, after she has edited it. A request to the reply or close tool would be refused, and those tools are not in the app's list.
- The escalation lands in engineering's tracker. The app calls the issue tracker connection to create the bug with the conversation summary attached. That creation tool is allowed, so it goes through.
- The shared host keeps the same rules. OpenClaw on the team's support host has its own authorization with the same lookup tools and the issue-creation tool, for teammates who work from chat instead of a desktop app.
- Activity shows the trail. Each call lists the app, the connection, the tool, the outcome and the timing. Activity excludes request arguments and results by default; storing them requires optional debug capture.
Tool names here are examples. When you edit access, Toolstile shows the real names your server exposes.
What changes for the team
- Context before the first reply. Bring conversation history and relevant articles into one place before writing the response.
- Drafts from the app, sending from the help desk. Where the help desk server exposes lookup and reply as separate tools, you allow lookup and leave reply out. The app can draft; a person sends.
- A clean handoff to engineering. Allow the issue tracker's creation tool and the app files the bug with the summary attached, so engineers get the context without a second write-up.
- One help desk account, no shared password. A contributor shares their account to a team entry, an admin approves it, and every authorized app uses it through Toolstile.
- One address for a shared host and every laptop. Hermes Agent or OpenClaw on the host, Claude Desktop on each laptop: all point at Toolstile with their own access.
Suggested access for a support workspace
| App and device | Connection | Allow | Block |
|---|---|---|---|
| Claude Desktop on Priya's laptop | Help desk | Conversation search and read tools | Reply, close and delete tools stay unavailable |
| Claude Desktop on Priya's laptop | Knowledge base | Article search and read tools | Article editing stays unavailable |
| Claude Desktop on Priya's laptop | Issue tracker | Issue search, read and create tools | Issue deletion |
| OpenClaw on the support host | Help desk and knowledge base | The same lookup tools | The same reply, close and edit tools stay unavailable |
| OpenClaw on the support host | Issue tracker | Issue search and create tools | Everything else stays unavailable |
Share the help desk account across shifts
In a team workspace, the person who owns the help desk account contributes it to a shared entry and an admin approves it. Apps with access use it through Toolstile, without copying the server credentials. New teammates join the workspace, authorize their app and receive an explicit grant for that shared entry.
If that account needs a fresh sign-in, calls to the help desk connection stop until someone reconnects it. Other available connections can continue; Toolstile does not switch to another member's identity. Before a contributor leaves, they can hand the shared account over to a teammate.
Set it up before the next shift
- Connect your help desk, knowledge base and issue tracker remote MCP servers and sign in to each account.
- Point Claude Desktop at Toolstile, or connect Hermes Agent or OpenClaw on the host following their vendor's remote MCP documentation, and approve each from the app.
- Pick the tools each app may use. Start with search and read tools, then add the issue-creation tool for escalations.
- Load the permitted tool list in the dashboard to confirm what each app can see.
Questions support teams ask
Can the app reply to customers by itself?
Through Toolstile, only if an allowed tool supports that action. Leave separate reply and close tools unavailable when you want a lookup workflow. A tool that combines lookup and reply must be allowed or blocked as a whole. Toolstile has no approval queue and cannot control actions in a help desk window signed in directly.
Are conversation contents saved in activity?
Activity records metadata by default, including the app, connection, tool, outcome and timing. Optional debug capture can store size-limited arguments and results for up to 24 hours. Diagnostic messages can contain information returned by a service; review data handling before connecting customer conversations.
What happens when the help desk sign-in expires?
The connection shows that it needs attention, and calls to it are refused rather than switched to another account. Reconnect the account once in the workspace so authorized apps can use it again. Other available connections can continue in the meantime.
Start with one help desk and one laptop
Connect the help desk, point one app at Toolstile and look up the first customer's history with the tools you chose. Your personal workspace starts free with 5,000 operations a month.