Discussion and Feedback on Dev MCP

The next release of the plugin (26.6.85) is coming early next week. Here’s a sneak peek at the release notes:

New tools: view object version history and past versions

New execution behavior: Locked objects now reject edit attempts with a clear error

New diagnostics tool for troubleshooting and getting version info for bug reports

Tool Fixes

• Document and folder descriptions are viewable
• Changing document metadata no longer versions the document
• Changing folder metadata no longer results in a new version
• Fixed record type deletion feedback for agents
• Fixed swimlane assignment and serialization in process models
• Adding a new site page no longer causes existing site pages to be recreated and lose configurations
• Date, datetime, and time types now function reliably for constant values and for testing inputs
• Application creation works for non-admin Designer users
• Record types and web APIs can be edited immediately after creation for non-admin Designer users
• testProcessModel correctly handles record-typed parameters

Auth and Ops

• MCP server now auto-trusts corporate certs (users no longer get SSL errors on corporate networks)
• Users no longer need to set LCP_API_PATH in their config
• Multi-user auth improvements (users prompted less frequently)

Thank you so much for the plugin and allowing us feedback. We found that translation sets seem to not be supported. Do you plan to add support?

I have been using this extensively the last week as I am trying to create a sales demo.  In this process i have found a few issues.

1 - AI Skills.  DevAgent when it modifies them, actually messes them up and I need to re-create them.  It changed the input parameters and needless to say the AI skill does not work after that.  The visualization in the process model is also incorrect.  Unsure how/why it does that, but it is an issue

2 - Given #1, I asked it to fix some json output from the AI Skill but do not modify the AI skill.  IT modified the AI skill anyway.  It also thought there was an error in the AI Skill so ti tried to fix it and back to #1

3 - Many times it tried to fix a process model and gets stuck trying to fix it.  It spent 7 hours tryiung to fix an issue.  It should stop or ask for some guidance.  But within Claude, using the DevMCP, it spent that time re-fixing the same error over and over./  Fixed for a “known” issue.  that caused the same problem so it went back to the previous code and just kept spinning.  I stopped it and had to redo the entire task as it did not work at all.

4 - more interesting type feedback, when working with record types in the code, it does not always work.  IT uses UUID and then in the code it does not reconcile correctly so we need to re-code the exact same thing.  And when you do see the real record name listed it is not understood, even though it looks correct.  These issues are not consistent so I cannot explain any pattern.

The composer fix was a biggy and that also apparently fixed the Dev Agent.  I have found the Dev Agent o behave better than the devMCP in its ability to get it right he first time.  I would assume there is additional context in that agent that the MCP/Claude does not have which makes sense.

In using the MCP, I am using it to help write scripts for a process model due to inconsistent results in updating process models.  I wanted a script hat would create a record to use in the writeRecord smart service.  For some reason it used the recordtype.update methos vs the direct assignment.  

I also tried again to use MCP to create a process model to read a record and then write to a different record and loop for each.  I had to updated every step.  It create the base structure, but I needed to fix each step.  I did use the mcp to try and fix each step but it took many iterations to do so and sometimes a google search gave me the answer.  While I am not providing specific here, let me know what would be helpful in providing feedback to help the product improve.

As I work through this demo via MCP, here is a question.  The section and grid control and and I sure others, when asked to create them it does so in expression code only.  FOr example, I see the grid control, but in the designer I can not select it as a control to see the data and anything from the the UI control panel.  It is code only to make any changes.  Is there a way to use the prompt differently or is that how the MCP (and the DevAgent) work?

In working with the MCP and DevAgent (both do the same here), I create a grid control, for example.  I want to make a quick change to the grid, like adding a column.  I open the interface and attempt to go to the UI control and it is not really there.  I finally get to it, and the entire grid is built from an expression.  So I need to code the new column instead of using the UI grid control.  This means I have to use AI to more easily update the expression code.  One, the update is time-consuming; it takes a few minutes, whereas using the UI control takes 10 seconds.  This makes maintaining the solution expensive.  This is kind of OK for a quick demo, but I cannot use this for a production solution.  Is this going to change?   I think this is a big issue.  It does this for all UI controls as far as I have seen,

Hi, I'm trying to set up Appian Dev MCP (the full read/write version, not the read-only variant) on an Appian Community Edition tenant and I'm stuck on the bundle download step.

Environment:

• Appian platform version: 26.6
• Plugin version: Appian Dev MCP 26.6.80 (confirmed deployed and active in Admin Console → Plug-ins, with servlets listed: LCP API, LCP Debug, LCP MCP Server Bundle Download)
• Per the docs (https://docs.appian.com/suite/help/26.6/devmcp.html), visited https://<my-site>/suite/plugins/servlet/stateless/downloads while signed in, to download appian-dev-mcp-server-bundle.tar.gz.

Result: Getting an Appian-themed "Error 404 - Page Not Found" on that URL.

Things I've ruled out:

• Confirmed I'm signed in and the plugin shows active on both.
• The URL matches the docs exactly, character for character.

I noticed the companion "Appian Dev MCP (read-only)" listing mentions: "until late June 2026, using this on your site may require a support case to turn on the correct feature toggle." Since these two plugins presumably share the same underlying download servlet mechanism, I'm wondering if that toggle still applies to the full version too — and specifically whether:

• Community Edition tenants weren't included in that toggle rollout, or
• Community Edition isn't actually supported by this plugin yet, or
• there's a different/updated download path I'm missing.

Could someone confirm whether Appian Dev MCP (full version) is expected to work on Community Edition, and if a feature toggle still needs to be enabled on our tenants? Happy to provide tenant details/logs if useful.

Thanks!