Dear Developers,
We’re excited to announce the launch of our Agentic Developer Toolkit. A suite of Agent Skills and Developer MCP server to enable you to build and ship quality apps faster in the age of Agentic development.
With this, you can go from an app idea to a quality app that is published to Freshworks as a custom app within minutes using the AI tools you already use. This includes Cursor, Claude Code, OpenAI Codex, GitHub Copilot, or any agent-friendly IDE.
Why this matters
The Agent Skills ecosystem encodes platform knowledge, conventions, and validation behavior into repeatable workflows. Your agent doesn’t need you to paste manifest rules, OAuth pitfalls, or FDK validate quirks every time. Instead, the skills carry that context, so you get fewer wrong turns and more Platform 3.0-aligned output by default.
Pair that with fw-dev-mcp for app publish flows, and you get a path from local repo to pack, upload, and submit without leaving your editor story.
Feedback we heard
Based on developer feedback, we identified several recurring friction points in the existing app development journey, including:
- Setting up the workspace with the right version of NodeJS and FDK, which often resulted in installation errors and manual troubleshooting
- Keeping up with the latest platform changes, feature releases, and applying them to the app
- Adhering to the app code to platform validations and code review guidelines with updated features, which were mostly identified during the app review process
- Publishing and maintaining different app versions (required manual zip upload each time)
- FDK lint validations and error fixes were manual and required code refactoring with platform version updates
- Node and FDK path issues post installation and FDK lifecycle management, such as upgrade, downgrade, and switch between versions.
What we built
We’ve packaged the experience into 5 purpose-built agentic skills available in our public GitHub repository:
- The Setup Skill
- The fw-setup, is a curated skill to install and manage FDK and Node.js. Get unstuck with /fw-setup-install, /fw-setup-upgrade , /fw-setup-status, /fw-setup-troubleshoot and more
- The App Development Skill
- Build Platform version 3.0 apps end-to-end using platform features with proper structure, manifest, requests, OAuth, serverless, Crayons UI, and help in fixing validation issues.
- Includes paths to migrate your apps from platform version 2.x via /fdk-migrate
- Supports fixes via /fdk-fix and quick checks via /fdk-review.
- Supports in fixing fdk validation issues, such as to reduce function complexity (≤ 7) via /fdk-refactor
- The AI Actions Skill
- A skill that is built around real automation patterns using actions.json
- Supports integrations with AI agent studio for SKUs and enhanced automations
- The Review Skill
- Performs Structured audits before app submission. It checks for app config, frontend changes, security-oriented checks, etc, which results in fewer surprises at review time and reduced app rejections and TAT for marketplace apps.
- The Publish Skill
- Allows you to validate, pack, upload, submit/update custom apps listing versions via fw-dev-mcp (uses JWT from Developer Portal)
- Enables you to manage new and existing custom apps directly from your agentic editor with in-development app support.
Furthermore, we added MCP tools to manage the app lifecycle. It now supports additional tools, which allow you to list your custom apps, list app versions, and create the app upload URL. It supports app publishing for custom apps as an in-development app. It helps you update existing apps by adding a new version and checking the app deployment status. Checkout Developer MCP Server documentation to know more
How it Helps You:
- Faster idea to working app with shorter development cycle (hours vs days/sprints)
- Reduced dependency on manual validation and debugging
- More consistent, platform-compliant apps
- Ability to scale development with leaner teams
- Repeatable, agent-driven workflows
How to Get Started? (takes ~30 seconds)
Use the command below to install skills and configure your Developer MCP server. That’s all you need.
npx skills add https://github.com/freshworks-developers/fw-dev-tools
Why we’re confident
We didn’t ship this lightly.
- We stress-tested these workflows, and here is how
- We built 30 medium-to-high complexity apps based on realistic marketplace scenarios
- We benchmarked it against 112 apps with varying levels of complexity.
- The outcome we’re seeing internally is a clear step up in productivity:
- Faster iterations
- Less repetitive debugging
- More consistent, platform-aligned outputs.
FAQs
Q. How do I configure the MCP Server?
The Developer MCP server is now generally available. Navigate to your Developer Account, generate or copy your API key by filling in details as applicable, and use “Connect to Developer MCP server” for your IDE, such as cursor or copy the settings, you can then configure in mcp.json. Ensure you have at least one active product subscription to generate the API key.
Q. Can I use the same Token for Freshdesk and Freshservice in one multiproduct app?
No. Currently, tokens are product accounts scoped. You will need to use the API Key for the respective product from the App Management Portal. The app will be uploaded to that specific product account. In case you fail to do so, even if the app is successfully uploaded to the developer portal, you won’t be able to use it inside products. For instance, use the Freshdesk key to publish apps for Freshdesk and likewise.
Q. Where do I get help for this toolkit vs Freshworks platform questions?
Use GitHub Issues for problems with installing or using this repo (skills, Cursor/Claude/Codex, plugins, rules, publish MCP as wired here) or drop us an email at skills@dev-assist.freshservice.com Use Freshworks Developer Community Forum for platform APIs, product behavior, and API keys / MCP setup from Freshworks. Interactions in this repo are expected to follow the project Code of Conduct.
Q. Which SKUs support AI Actions Apps?
- AI Actions are supported on these subscriptions: Freshsales Suite, Freshdesk Omni, Freshservice ESM, Freshservice ITSM, Freshchat
- They are not supported on: Freshcaller, Freshsales Classic, Freshdesk Legacy, Freshservice MSP
Q. Does “publish” in this toolkit allow uploading apps for every product?
No. Building and validating with fw-app-dev, follows Platform 3.0 and the modules in your manifest across the products those modules apply to (for example Freshsales Suite, Freshchat, Freshcaller, and others per the official SDK). Marketplace upload and submit via fw-publish and the Developer MCP server in this repo is supported only for Freshdesk and Freshservice custom apps. For other products, use the deployment or distribution path described in Freshworks marketplace and product documentation.
We’re eager to hear your feedback!
This is a real shift in how Marketplace apps can be built. It’s faster, more accurate, and more repeatable with agents. Try fw-dev-tools on your next app development or migration. Tell us what worked and what didn’t, and help us prioritize what comes next. You may share your feedback at skills@dev-assist.freshservice.com.
Happy shipping.
Regards,
Team Freshworks Developers