Hey Pickaxe community! @nathanielmhld just dropped a super helpful video that walks through three big features that are fresh in Pickaxe.
Here’s what’s inside:
What is an MCP?
MCP stands for Model Context Protocol. It’s a simple way to connect your Pickaxes to other apps and services, so you can pull in data, automate tasks, or even let your Pickaxe take action (no coding needed!). Nathaniel shows how you can use built-in MCPs like OpenAI Web Search, or connect to Notion and other tools using services like Smithy.
Pickaxe API in Action
You’ll see how to set up and use the Pickaxe API to run your Pickaxe from other platforms, like Make.com. Nathaniel gives a step-by-step demo of how to send and receive data so you can automate things like responding to customer emails.
Studio API for User and Document Management
Learn how the new Studio API lets you add or remove users, invite people to your studio automatically, and manage documents (all through simple API calls!).
There’s even a sneak peek at what’s coming soon: a Pickaxe-powered MCP that will make connecting and managing everything even easier.
Check out the new tutorial here:
Give it a watch and let us know if you try any of the new features or have questions. We can’t wait to see what you build!
Quick question with regards to how MCPs work in terms of privacy.
I’m currently in the process of building out a business proposal for the use of Pickaxe within the company I work for and I’ve been asked to include a section on data privacy and security as the data that we would be using for some of the studio could be sensitive data (cost prices, customer names, etc)
How does Pickaxe handle data privacy and security and is it GDPR compliant?
Also in the demo above it talks about finding 3rd party sites to connect to MCPs how secure is it connecting to different services like this? Is there any chance that data transferred through these MCP servers and intermediary sites could be hacked and the data being shared be accessed?
I know that Pickaxe can’t tell me about these other 3rd party services, but maybe you tech team would know if it would be wise for users be aware of any potential risks to using MCP and could recommend any specific checks that users should be performing before taking data submitted by their customers and passing it through these MCP services.
Be cautious with MCPs — your concerns are valid.
If you’re integrating with an official server, like Make’s MCP, you’re protected under their privacy policy (Make, for example, is GDPR compliant).
The real risk comes from using unofficial or random servers found on GitHub. In those cases, there are no guarantees around security or data privacy — you’re essentially trusting unknown code with sensitive data.
What is an MCP?
Pickaxe API in Action
Studio API for User and Document Management
There’s even a sneak peek at what’s coming soon: a Pickaxe-powered MCP that will make connecting and managing everything even easier.
