We just shipped something we're really excited about in v1.3.0: API Keys and REST API access, along with MCP server configuration for AI assistant integration.
Here's the problem we're solving: you have tools and workflows that work for you, and StashSync should fit into your world, not force you into a new one. Today we're opening StashSync up to that.
What's New in v1.3.0
1. API Keys – Programmatic Access to Your Data
You can now generate API keys directly from Settings and use them to programmatically access your StashSync data. This means:
- Automation: Use n8n, Zapier, Make, or custom scripts to automate your StashSync workflow
- Integration: Connect StashSync to other tools in your stack (project management, note-taking, knowledge bases)
- Custom tools: Build your own integrations tailored to your specific workflow
Each API key is scoped to your account and displays exactly once when created—store it in a password manager or secrets vault. You can manage multiple keys and revoke them anytime.
Learn more about creating and managing API keys →
2. REST API Reference – Everything You Need to Build
The new API Keys tab includes an inline REST API reference panel listing all available endpoints. You'll see:
- Notes endpoints - create, read, update, search notes
- Bookmarks endpoints - save and manage bookmarks
- Stashes endpoints - organize content into collections
- Tags endpoints - manage and query tags
- Search endpoints - full-text search across your library
You don't need to hunt through docs. The reference is right there in the app, ready to use.
3. MCP Server Integration – Talk to Your AI Assistant
Here's the exciting one: Model Context Protocol (MCP) lets you connect StashSync to AI assistants.
Imagine this:
You're in Claude Desktop working on a research project. You say: "Find my notes about CRDT algorithms and summarize them." Claude searches your StashSync library and gives you the summary. Then you say: "Save a bookmark about distributed systems and tag it 'research.'" It's saved instantly in StashSync.
That's what MCP enables. It's a protocol that lets AI assistants read, write, and search your StashSync data without leaving their interface. All your notes, bookmarks, and files become part of the AI's context.
Supported AI assistants include:
- Claude Desktop
- Cursor
- Other MCP-compatible clients
Why This Matters
For Power Users & Developers
You can now build custom workflows. Imagine:
- Automatically save articles from your RSS feed as bookmarks in StashSync
- Extract data from emails and file them in StashSync
- Generate weekly digests of your research notes
- Sync StashSync with your project management tool
The REST API is your playground.
For AI Assistant Users
Your StashSync library becomes part of your AI assistant's memory. Instead of copying and pasting information, your AI can search your actual notes and bookmarks. It's like giving your AI assistant a direct line to your personal knowledge base.
For Everyone Else
You don't need to use APIs or MCP. They're there if you want them. Your core StashSync experience—saving notes, bookmarks, and files—works exactly the same. But now the door is open to deeper integration with your existing tools.
Privacy & Security
Your data stays on your devices. Here's how:
- API keys authenticate requests to our servers, which act as sync coordinators—not data vaults
- MCP integrations are stateless - each request is independent, no persistent session tokens
- You control access - generate keys, revoke them anytime
- Rate limits protect your account - 120 requests per minute per key
API keys should be stored securely (password manager, environment variables, secrets vault). If compromised, revoke immediately and create a new one.
Getting Started
Creating an API Key
- Open StashSync Settings
- Go to the API Keys tab (new!)
- Click Create API Key
- Copy it immediately—it won't display again
- Store it securely
Setting Up MCP
If you use Claude Desktop or another MCP-compatible AI assistant:
- Open StashSync Settings → API Keys tab
- Look for MCP Configuration (or follow the setup guide below)
- Add your StashSync API key to your AI assistant's config
- Restart the assistant
- Start asking it to search and save to your StashSync library
Using the REST API
The API reference is built into the app (Settings → API Keys tab). For common use cases:
- Save a bookmark via automation: POST
/v1/bookmarks - Search your notes: GET
/v1/notes/search?q=... - Organize with tags: POST
/v1/tags
What's Next?
We're still expanding integration possibilities. Future plans include:
- More pre-built integrations with popular platforms
- Webhook support for event-driven automation
- Broader AI assistant support beyond MCP
One More Thing
This is version 1 of our integrations layer. We're building this based on your feedback. If you're using these APIs or MCP:
- Tell us what works
- Tell us what breaks
- Tell us what you'd build if we exposed a different API
- Tell us what platforms you want to connect to next
Your workflow matters. We're here to fit into it.
Summary
StashSync is now more than a standalone app—it's a platform for your information. Use the REST API to automate your workflow. Use MCP to think alongside AI assistants with your data at hand.
Your notes, bookmarks, and files. Your tools. Your way.
Explore API Keys in your StashSync Settings →
FAQ
Q: Is my API key secure?
A: Yes. Store it like a password—in a password manager or secure vault. Don't commit it to version control. If exposed, revoke it immediately.
Q: Can I use the same API key across multiple tools?
A: Yes, but we recommend creating separate keys for each integration. That way, if one key is compromised, only that integration is affected.
Q: Do I need an API key to use StashSync normally?
A: No. API keys are only for programmatic access (scripts, integrations, AI assistants). Regular app usage works as before.
Q: Can I use MCP with AI assistants other than Claude?
A: Yes—any MCP-compatible client (Cursor, other emerging platforms). See the MCP guide for setup.
Q: What's the rate limit?
A: 120 requests per minute per API key. That's plenty for most workflows.
Q: Can I see which integrations are using my API keys?
A: You can see active keys in Settings. We're planning better key management features (like usage logs) soon.