A: It's a connector that lets Claude Desktop talk to your Unanet system. Think of it as a translator between Claude and Unanet, allowing you to use natural language to work with your projects, timesheets, and reports.
A: No! The setup guide is written for non-technical users. If you can install software like Microsoft Office, you can install this.
A: No, this is a third-party integration tool that uses Unanet's official API. It's like how Outlook can connect to Gmail - different companies, but they work together.
A: The MCP server itself is free and open source. You need:
- Claude Desktop (check Claude's pricing)
- Unanet API access (included with most Unanet subscriptions)
A: Node.js is like Microsoft .NET or Java - it's a runtime that allows the connector to run. It's free, safe, and used by millions of developers.
A: We recommend C:\UnanetMCP\ for simplicity. Avoid:
- Program Files (permission issues)
- OneDrive folders (sync conflicts)
- Network drives (connection issues)
A: Check with your IT department first. You'll need:
- Permission to install software
- Access to Unanet API
- No conflicts with security policies
A: Usually 10-15 minutes if you have all your credentials ready. First-time Node.js installation might add 5 minutes.
A: Yes! Your credentials are:
- Stored locally on your computer only
- Never sent to third parties
- Encrypted when talking to Unanet
- Same security as using Unanet directly
A: Only you. The connection is:
- Your Computer → Claude Desktop → MCP Server → Unanet
- No cloud storage or external servers involved
A: They would need:
- Your Windows login
- Your Claude Desktop access
- Knowledge of what commands to use Same risk as having Unanet bookmarked in your browser.
A: No. It only does what you tell it to do, using the same permissions as your Unanet account. If you can't do something in Unanet normally, Claude can't do it either.
A: Windows 10 and Windows 11. Windows 7/8 might work but aren't tested.
A: Yes! The core server works on all platforms. This guide is Windows-specific, but Mac/Linux users can follow the technical README.
A: Version 18 or higher. The installer from nodejs.org will give you the latest stable version.
A: Yes, but you'll need to:
- Move the folder
- Update Claude Desktop config with new path
- Restart Claude Desktop
A: Ask Claude things like:
- "Show me all active projects"
- "Submit 8 hours to project ABC for today"
- "Generate a project profitability report"
- "Create a new contact for John Smith"
- "What's the budget status for project XYZ?"
A: No! Use natural language. Claude understands variations:
- "Show projects" = "List my projects" = "What projects do I have?"
A: Each person needs their own installation with their own Unanet credentials. It's tied to individual Unanet accounts.
A: No. You need internet to connect to Unanet, just like using Unanet in a web browser.
A: Usually means:
- You haven't restarted Claude Desktop after setup
- Configuration file has wrong path
- Credentials aren't set correctly
See Troubleshooting Guide for fixes.
A: Check:
- Did your Unanet password change?
- Is Unanet down for maintenance?
- Did Windows Update restart your computer?
A: Normal response time is 2-5 seconds. If slower:
- Check internet connection
- Try simpler queries first
- Unanet might be under heavy load
A: Yes! Simply:
- Delete the UnanetMCP folder
- Remove the "unanet" section from Claude Desktop config
- Optionally uninstall Node.js from Control Panel
A: In order:
- Check the Troubleshooting Guide
- Ask your Unanet administrator
- Contact your IT support
- Check the GitHub repository issues
A:
- What step failed
- Exact error message (screenshot helps)
- Windows version
- When it last worked (if ever)
A: Check the GitHub repository for:
- Issues others have solved
- Feature requests
- Tips and tricks
A: Share the guide, not your credentials! Each person needs their own API key.
A: Check the GitHub repository monthly for updates. Updates usually add features or fix bugs.
A: Advanced users can modify the code. Basic users should stick with the provided features.
Don't see your question? Check the full documentation or open an issue on GitHub!