Shimo Docs MCP. Manage every file and audit log without opening a browser.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Shimo Docs MCP Server connects your AI agent directly to a professional document management system. It lets you list, create, import, and export structured files—Word, Excel, PPT equivalents—without ever touching the web interface.
Your agent handles file operations, folder navigation, user lookups, and compliance audits through natural conversation.
What your AI agents can do
Create file
Creates a brand new document (Word, Excel, or PPT equivalent) within Shimo Docs and returns its file ID.
Export file
Converts an existing Shimo Doc file into a standard format like PDF or DOCX.
Get file
Retrieves the specific metadata and details for one known file ID within Shimo Docs.
The agent runs list_audit_logs to provide a chronological list of who accessed what, and when.
You can use create_file, get_file, and export_file to manage the entire file lifecycle within Shimo Docs.
The agent runs list_files and list_folders to map out the current structure of your workspace, letting you pinpoint assets quickly.
You use import_file to bring external data (like a CSV) directly into an existing Shimo document for collaboration.
The agent calls list_users or get_org_info to confirm user roles, organizational details, and metadata compliance.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Shimo Docs MCP Server: 10 Tools for Document Management
Use these ten tools to control file operations—creating, listing, exporting, importing, and auditing—within a professional document suite via your AI agent.
019d847fcreate file
Creates a brand new document (Word, Excel, or PPT equivalent) within Shimo Docs and returns its file ID.
019d847fexport file
Converts an existing Shimo Doc file into a standard format like PDF or DOCX.
019d847fget file
Retrieves the specific metadata and details for one known file ID within Shimo Docs.
019d847fget folder content
Lists all files and sub-folders contained directly inside a specified parent folder path.
019d847fget org info
Retrieves high-level metadata about the entire organization, like name and primary contact details.
019d847fimport file
Ingests external data (like a CSV or raw document) and places it into an editable Shimo Doc file.
019d847flist audit logs
Generates a detailed history of activity, showing who did what across the workspace and when.
019d847flist files
Provides an exhaustive list of every single file ID currently accessible in your entire Shimo Docs account.
019d847flist folders
Lists all available top-level and sub-folder paths within the Shimo Docs workspace structure.
019d847flist users
Returns a list of all user accounts registered in the organization, including their roles and IDs.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Shimo Docs, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Listen up. Shimo Docs connects your AI agent right into a professional document management system—a full-blown corporate file cabinet. Forget clicking around web interfaces or wrestling with folder permissions; your agent treats this whole thing like simple data endpoints, and it's slick.
When you hook up your client to this server, you get total control over your company docs. You don't need to know the complex directory path for a file; your agent handles that mess for you using direct tool calls. This means your AI can manage everything from creating brand new documents to auditing who touched what last week.
To handle the whole lifecycle of your assets, your agent uses create_file to build a fresh document—whether it's a Word file, an Excel sheet, or a PowerPoint equivalent—and gets you that crucial file ID right off the bat. If you need to convert one of those existing Shimo Docs into something standard for sharing, say a PDF or DOCX, it runs export_file.
To check what a specific asset is all about, even if you know its file ID, your agent calls get_file and pulls back all the metadata details. If you've got external data—like a raw CSV dump from accounting or some text notes—you use import_file to ingest that stuff and stick it into an editable Shimo Doc for collaboration.
Mapping out what’s where is another thing your agent nails. If you gotta know exactly what folders exist in the system, it runs list_folders. To see every single file ID currently living in your whole account, no matter how deep it is, it just executes list_files. For a granular view of one specific folder—the actual contents and sub-folders inside that parent path—it hits up get_folder_content.
On the organizational side, your agent keeps tabs on who's doing what. To get an exhaustive list of every user account registered in the organization, complete with roles and IDs, it runs list_users. For high-level compliance checks or just knowing how big the operation is, it uses get_org_info to pull back metadata about the whole company, like the main name and primary contact details.
And when you gotta know if someone accessed a file, who changed permissions, or what happened across the workspace, your agent runs list_audit_logs. This spits out a detailed history, showing exactly who did what and when.
It's all about structure and compliance. You can use the tools to run deep audits using list_audit_logs that gives you a chronological record of activity across the entire workspace. For navigating your data, it maps out every top-level or sub-folder path with list_folders and lets your agent list every single file ID in the whole system via list_files.
If you need to know what specific files are sitting inside one folder, it runs get_folder_content.
When it comes to keeping everything current, if you've got external content—say a massive spreadsheet dump—you feed it directly into an existing document using import_file, so your team doesn't lose time manually transferring data. Need to make something new for the next quarter's budget? You use create_file and get that file ID instantly.
If you need to review what details are attached to a known asset, it fetches those specifics with get_file. For checking organizational standing, your agent confirms user roles by calling list_users, or checks overall metadata compliance using get_org_info. The whole setup lets your AI client manage the entire file lifecycle—creation, retrieval, export via export_file, and ingestion—all without you ever touching a web browser.
It keeps all that corporate data organized.
How Shimo Docs MCP Works
- 1 Subscribe to this server on Vinkius. You'll need your Shimo App ID and App Secret.
- 2 Connect your preferred AI client (Claude, Cursor, etc.) to the MCP Server endpoint using those credentials.
- 3 Ask your agent a task: 'Create a new Q3 plan in the Marketing folder.' The agent runs
create_file, then maybeget_folder_contentto find the right spot. You get confirmation and a file ID back.
The bottom line is, you tell your AI client what needs doing with corporate files; the server executes the steps via specific tools, keeping you out of the web UI.
Who Is Shimo Docs MCP For?
This is for anyone whose job relies on structured company data. If you spend time navigating cloud drives or manually tracking document versions, this saves you clicks. We're talking Project Managers who need to audit documentation progress and Admin teams who have to track user access.
Needs to use list_files and get_folder_content to check if all project stakeholders have uploaded their required documentation before the deadline.
Uses list_users and get_org_info to audit permissions, ensuring only authorized staff can view sensitive folders. They also run list_audit_logs for compliance records.
Needs to use import_file to pull raw data from an external source and quickly map it into a shared, editable spreadsheet without manual copy-pasting.
What Changes When You Connect
- You stop clicking through folder trees. Instead, run
list_filesto get an immediate inventory of all documents across the entire workspace in one API call. - Compliance checks are fast. Running
list_audit_logsgives you an instant, queryable timeline of who viewed sensitive files and when—crucial for governance. - Collaboration becomes direct. Use
import_fileto pull external data into a document; the agent handles the mapping so you don't have to copy-paste anything. - Project setup is controlled. Need a new shared workspace? Tell your agent to run
create_fileand give it a structured name, getting back the ID immediately for the next step. - You never lose context again. The combination of
get_folder_contentandlist_folderslets you map out complex organizational structures simply by asking the agent.
Real-World Use Cases
Compliance Audit: Who touched the HR files?
An admin needs to know if any contractor accessed the Q4 salary sheet. Instead of searching through three different permissions dashboards, they ask their agent to list_audit_logs for that specific document ID. The agent immediately returns a filtered list showing every user who opened it and when.
Board Meeting Prep: Consolidating data.
A PM needs the latest budget numbers from Finance (Excel) and the marketing strategy summary (Word). They instruct their agent to import_file twice—once for each source. The agent combines the raw content into a single, editable 'Q3 Summary' file using create_file.
Onboarding New Team Members.
A manager needs to confirm that all new hires have access to the correct departmental folder structure. They ask the agent to run list_users, cross-reference those IDs with get_org_info for department roles, and check if the user is listed in key shared folders.
Archiving an Old Project.
The team needs to archive all documents from 'Project Phoenix.' They ask the agent to first run list_folders to confirm the path, then use get_folder_content to list every file ID. This provides a definitive manifest of what must be archived.
The Tradeoffs
Trying to get content without the ID.
Asking, 'Show me the Q2 report for marketing.' The agent fails because it doesn't know which specific file instance you mean. It can't guess a document path or name.
→
Guessing folder structure details.
Telling the system, 'The client files are in the main drive under Finance/2024.' If any subfolder is misnamed or missing, the call fails immediately and provides no useful context.
→
Manual data entry for updates.
Needing to update user roles and then manually generating an audit log based on that change. This process creates massive human error risk.
→
→
Always start with list_folders or get_folder_content to confirm the exact path. Then, use list_files to get a comprehensive list of file IDs before attempting any modification using create_file or import_file.
When It Fits, When It Doesn't
Use this server if your workflow involves highly structured corporate data (Word, Excel, etc.) and requires rigorous audit trails. If you need to track who saw what, when, and where—you need the full suite of tools: list_audit_logs, get_file, and list_users.
Don't use this if your goal is simple web scraping or pulling public data from a website. This server only connects to Shimo Docs, an enterprise file system. If you just need a plain text list of links, a standard browser API is better. But if you need to create, modify, and audit files in a controlled environment, this set of tools is necessary.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Shimo Docs. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Document management shouldn't feel like navigating a corporate maze.
Today, getting the full picture means clicking from the main drive to the department folder, then into 'Final Drafts,' and hoping you don't accidentally open the outdated version. You copy file names, check versions manually, and waste time confirming if all necessary documents are actually present.
With this MCP server, that whole process vanishes. You ask your agent to `list_files` for a project ID. It doesn't matter how deep in the folder structure it is—you get a single list of every file available. That’s it.
Shimo Docs MCP Server: Get full control over your corporate data.
Manual tasks include checking user permissions across departments, exporting dozens of files to PDF for review, and compiling a list of all current project owners. Each task requires jumping between different admin tools and services.
Now, you run the agent once. You tell it, 'List all active users and check their roles.' The server runs `list_users` and `get_org_info`, returning clean data instantly. It keeps everything in one conversation.
Common Questions About Shimo Docs MCP
How do I list every file in my Shimo Docs account using the list_files tool? +
Run list_files with no parameters to get a full manifest of all accessible files. This is faster and more comprehensive than trying to use get_folder_content multiple times.
Can I check who used the system using list_audit_logs? +
Yes, that's what list_audit_logs does. It gives you a verifiable history of actions—who accessed which files and when. This is key for compliance.
What if I need to update user data? Should I use get_org_info or list_users? +
list_users gives you the roster, but get_org_info provides details about the overall organization's metadata. Use both when building a profile of the current setup.
I have external data; how do I get it into Shimo Docs? Which tool should I use? +
You need import_file. This tool takes raw, external content and properly places it into a collaborative document within the system.
How do I get detailed metadata for a single document using the get_file tool? +
It returns all structural information about one file, not just its name. You'll see details like the original creator, last modified date, and whether it's part of a specific folder structure.
I only know the folder path; how do I list everything inside using get_folder_content? +
This tool maps out the contents layer by layer. It lists every file, sub-folder, and its associated metadata within that specific directory structure.
When I use create_file, what do I need to know about naming conventions or formats? +
You must specify the desired file title and type (e.g., spreadsheet or document). The tool handles generating a unique ID and setting up the basic structure for immediate collaboration.
What does the export_file tool do, and what formats can I expect? +
It converts your active Shimo document into external standards like PDF or DOCX. It doesn't change the original file; you always keep the master copy intact.
How do I find my Shimo App ID and Secret? +
Log in to the Shimo Open Platform, create a new application, and you will find your App ID and App Secret in the application credentials section.
Can I export documents to PDF through the agent? +
Yes. Use the export_file tool with the file ID and specify 'pdf' as the type. Your agent will provide the link to download the exported document.
Is multi-user editing supported? +
Yes, Shimo Docs is natively designed for real-time collaboration. Any file you manage or create via this server can be shared and edited by multiple users simultaneously.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Hexomatic
Automate web scraping and worklfows via Hexomatic — manage workflows, recipes, and automation logs directly from any AI agent.
HiFlow
Workflow and business process management.
Miro (Visual Collaboration & Whiteboarding)
Manage collaborative boards via Miro — create sticky notes, list visual items, and audit team members.
You might also like
Maestra
Automate transcription, translation, and AI voiceovers via the Maestra.ai REST API.
Cognito Forms
Build smart online forms with conditional logic, calculations, and payment collection that adapt to every response.
Immich (Google Photos Alternative)
Manage your self-hosted Immich photo and video library — list assets, organize albums, and handle user administration via AI.