Design & Creative Tools · Cults + Claude
Cults MCP with Claude: Find and Manage 3D Printing Models Through Plain Language
The short answer
Claude works with Cults through the Model Context Protocol, an open standard that lets Claude securely search models, list designer storefronts, manage collections and review download history. Access uses an API key, and the organisation controls what Claude can read and change.
What is Cults?
Cults is a digital marketplace for 3D printing models. It connects designers and makers, letting creators share and sell printable designs while buyers discover a large range of files. Print shops, product teams, educators, hobbyist communities and small manufacturers all use it to source models quickly. Because the catalogue is large and varied, finding the right file and keeping track of purchases can take real time, which is where automation helps.
How Claude connects to Cults through MCP
The Model Context Protocol, or MCP, is an open standard that acts like a universal adapter between Claude and other software. It lets Claude use a tool securely, reading information and taking actions, with permissions your organisation sets. Cults offers its own MCP server, so Claude can work with the marketplace in a structured and controlled way.
Once connected with an API key, Claude can typically search models by keyword or category, list designer storefronts, manage collections and track download history. You can ask in everyday language, such as finding printable storage organisers under a certain size, and Claude carries out the lookup in Cults and summarises the results.
Permissions and approvals keep your team in charge. Access is limited to the actions you allow, and consequential steps such as changing collections can require a person to confirm first. Every action can be logged, so you always know what Claude did and when.
What you can automate
Sourcing models for a print shop
A print shop receives a request for custom replacement parts. Claude searches Cults for matching printable models, lists the designers and summarises licence terms and file details for the operations team to review before ordering.
Building curated collections for a product team
A product design team wants a shared library of reference models. Claude helps organise models into named collections, adds new finds on request, and removes outdated items after a team member approves the change.
Reviewing download history for compliance
A procurement lead needs to know which models the team has downloaded over a quarter. Claude pulls the download history from Cults and produces a clear summary by project, making audits and budget reviews faster.
Scouting designers for a campaign
A marketing team is looking for designers with a particular style. Claude lists relevant designer storefronts, compares their catalogues and provides a short shortlist with links to review internally, saving hours of manual browsing.
Supporting an education programme
A school technology coordinator needs printable teaching aids. Claude searches for models by subject and age group, groups them into collections for each class, and keeps a record of what has been downloaded for the term.
An end-to-end workflow: Monthly model sourcing and tracking for a print shop
TriggerA new customer order arrives in the company's ticketing or order system describing a part or design need.
Claude reads the order details from the ticketing system through its connection.
Claude searches Cults for matching printable models and filters by the requested specifications.
Claude lists the top candidates with designer names, file details and summary notes.
The operations manager reviews the shortlist and approves one model in the chat.
Claude adds the approved model to the client's Cults collection and records the download in the order file.
Claude posts a summary to the team channel for the production team to start printing.
OutcomeOrders move from request to print-ready file faster, with a clear record of every model used, which typically reduces manual searching and improves traceability.
How we set it up
Free automation audit
We review your current use of Cults and related systems to identify the workflows worth automating, such as sourcing, collection management or reporting.
Secure API key connection
We connect Claude to Cults through its MCP server using an API key. The key is stored securely and access is limited to the actions your workflow needs.
Workflow design
We map the end-to-end process across Cults and your other systems, including Microsoft 365, CRM, ERP or ticketing, and agree which steps need human approval.
Testing and launch
We test the workflow against real past requests, then launch with monitoring and audit logs so every action can be reviewed.
Team training
We train your staff on how to make requests, review results and approve actions, so the team stays confident and in control after launch.
Who benefits
- Print shop operations manager
- Finds suitable models faster and keeps a clear record of each file used in production.
- Product design lead
- Maintains shared model libraries and collections without manual admin work.
- Procurement or finance lead
- Gets accurate download history summaries for budgeting and audits.
- IT or department head
- Oversees a controlled, permission-based connection that can be monitored and audited.
Security and control
- Access uses an API key with least-privilege permissions, limited to the actions your workflow requires.
- People approve consequential actions, such as changing collections, before Claude carries them out.
- Every action is recorded in audit logs so your team can review what happened and when.
- Licence terms and designer rights are checked by your team before any model is used commercially.
- API keys are rotated and revoked on a schedule your IT team controls.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to meet internal data handling policies. Companies in India must consider the Digital Personal Data Protection Act, 2023, and we can host in India to support compliance. Organisations in the UAE and Saudi Arabia must meet local data protection laws, and we design hosting around those requirements. The hosting region is chosen during design to meet your specific legal and policy needs.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Cults MCP server do?
The Cults MCP server lets AI tools like Claude connect to the marketplace in a structured way. It typically supports searching models, listing designer storefronts, managing collections and tracking download history, so requests can be handled in natural language rather than through manual browsing.
Is it secure to connect Claude to Cults?
Security depends on how the connection is set up. We use an API key with limited permissions, store it securely, and require approval for consequential actions. Audit logs record activity so your team can review everything Claude does.
What can Claude do with Cults once connected?
Typically, Claude can search printable 3D models, browse designer storefronts, organise collections and review download history. You can ask for these tasks in plain English, and Claude summarises the results for your team.
How long does setup take?
Many setups take a few weeks, from the free audit through testing and launch. The timeline depends on how many systems are involved and how complex the approval steps are. We agree a realistic schedule during the audit.
Which plan or permissions do I need?
Access generally requires a valid Cults account with an API key that your organisation is permitted to create. The exact permissions depend on your account type and on what the workflow needs. We confirm this during the free audit so you know what to prepare.