Monday's campaign report, without the copy-paste
A weekly report can mean collecting exports from separate tools and pasting them into a document. Consider this example using the team's campaign and docs MCP connections instead.
- Mara asks for the numbers. From Claude Desktop on her laptop she asks for last week's results across the active campaigns. The app calls the campaign connection through Toolstile, which checks Mara's app has access to those read tools and forwards the request with the approved account.
- The draft comes from the docs tool. The app reads last week's report page and the brief for the next launch through the docs connection, so the new report follows the existing structure and the brief's goals.
- The app writes the report. Drafting is the app's job. Toolstile supplied the data and the context; it does not generate the text.
- The report is saved with the tools you chose. If the docs server exposes a separate page-creation tool, you can allow it to save the draft as a page. Leave separate email-send and campaign-launch tools unavailable; requests to those tools through Toolstile are refused.
- Another app can have narrower access. A separately authorized Grok Bot connection can use just the reporting tools. Any routine or delivery schedule is configured in that app.
- Activity shows who pulled what. Each call lists the app, the connection, the tool and the outcome. 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
- Real data, not last month's export. The AI app reads current campaign results, contact lists and page drafts through connections you approve.
- Research stays separate from publishing where the server allows. When a server exposes separate read and publish tools, you can allow one group and leave the other out. Where one tool does both, you decide for that tool as a whole.
- Share access without copying server credentials. Members contribute their own accounts and an admin approves them. Apps use the approved account through Toolstile, with no need to paste its token into a shared document or app config.
- One setup for every app. Claude Desktop today, a Grok Bot in the cloud next quarter: both point at the same Toolstile address and get the access you chose for each.
- A clear trail for the audit question. When someone asks which app read the contact list, activity has the answer.
Suggested access for a marketing workspace
| App and device | Connection | Allow | Block |
|---|---|---|---|
| Claude Desktop on Mara's laptop | Campaign or CRM tool | Search, report and contact-read tools | Send, launch and delete tools stay unavailable |
| Claude Desktop on Mara's laptop | Docs tool | Page search, read and create tools | Page deletion |
| Grok Bot in the team's cloud workspace | Campaign or CRM tool | Report-read tools only | Everything else stays unavailable |
| Grok Bot in the team's cloud workspace | Docs tool | Page read tools only | Everything else stays unavailable |
Share the agency account, not its password
Agencies, freelancers and new hires come and go. In a team workspace, the person who owns the campaign-tool account contributes it to a shared entry and an admin approves it. Everyone's authorized apps use it through Toolstile, and the password stays with its owner.
When that person leaves, they hand the shared account over to a teammate first, and the connection keeps working. If an account needs a fresh sign-in, calls to that connection stop until it is reconnected in one place. Toolstile does not quietly switch to another member's account.
Set it up before the next report
- Connect your campaign, CRM and docs remote MCP servers and sign in to each account.
- Point Claude Desktop or another remote MCP client at Toolstile and approve it from the app.
- Pick the tools each app may use. Start with search and read tools; add creation tools where you want drafts saved.
- Load the permitted tool list in the dashboard to confirm what the app can see.
Questions marketing teams ask
Will the app send an email or launch a campaign on its own?
Through Toolstile, only if an allowed tool supports that action. When send and launch actions are separate tools, you can leave them unavailable. A multipurpose tool must be allowed or blocked as a whole. Toolstile does not add a review queue or control actions outside its connections, such as a browser signed in directly.
Are request contents saved in activity?
Activity records metadata about each call 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 data.
Which marketing tools work with Toolstile?
Look for a remote MCP server on public HTTPS that exposes the campaign, CRM or docs tools you need. Toolstile does not turn a vendor's API into MCP or host that server for you. Check the provider's endpoint and authentication requirements, then add the connection.
Start with one tool and one report
Connect the campaign tool, point Claude Desktop at Toolstile and pull the first set of numbers into a draft. Your personal workspace starts free with 5,000 operations a month.