Skip to main content
john.rogers
Employee
Aug 7, 2026 6:31 PM UTC

Discussion and Feedback on Dev MCP

Have questions or feedback on the Appian Dev MCP? This is a great place to ask them. 

 

Appian’s Dev MCP plugin can be found on the Appian App Market here (https://appmarket.appian.com/listings/appian-dev-mcp), as well as a read-only version intended for production use or other environments where it’s important to avoid any design object changes (https://appmarket.appian.com/listings/appian-dev-mcp-read-only). 

 

Documentation and installation guidance can be found here: https://docs.appian.com/suite/help/latest/devmcp.html

And finally, our public repo of skills to install alongside the MCP can be found here. We welcome contributions if you’ve developed a skill or skill update you think would benefit other users. https://github.com/appian/dev-mcp-skills

    26 replies

    Show previous replies
    raulg0001
    raulg0001
    Inspiring
    Oct 24, 2026 10:42 AM UTC

    For a related action, instead of applying visibility permissions at the record level, it does so at the process level—which is inefficient, as the instance is always triggered, which shouldn't be the case.

     

     

    alvarog549347
    New Participant
    Nov 6, 2026 7:35 AM UTC

    Hi all,

    We're hitting a version-check refusal when using Dev MCP against our TEST site, while the same setup works on DEV.

    Environments:

    - DEV: Appian 26.6, Dev MCP plug-in 26.9.5, MCP server bundle built 2026-10-26 -> works.

    - TEST: Appian 26.9, Dev MCP plug-in 26.9.10, MCP server bundle built 2026-11-03 -> every tool is refused.

    Symptom: all tools except getDevMcpVersionInfo return:

    "Refused: the DevMCP plugin on https://<our-test-site> does not report which MCP bundle it was built with (The plugin's /meta endpoint returned 404...), so this MCP server cannot confirm the two match."

    getDevMcpVersionInfo reports plugin.available=false with the same 404 on /meta, while the MCP server half reports its own build info normally.

    What we've checked:

    - The MCP server starts and connects fine (stdio, same bundle as downloaded from the site).

    - LCP_API_PATH is not set in our config (only LCP_URL and LCP_AUTH_METHOD).

    - The plug-in is the latest version on the site (26.9.10).

    Questions:

    1. Is /meta expected to exist in plug-in 26.9.10 on Appian 26.9? Is it only served when the plug-in is enabled / a feature toggle is on?

    2. Is there a known issue with the plug-in servlets on Appian 26.9?

    3. Does anyone else running Appian 26.9 see the same 404 on /meta?

    Thanks!

    raulg0001
    raulg0001
    Inspiring
    Nov 6, 2026 9:52 AM UTC

    I am using version 26.9, and it works perfectly for me. I recommend that you update the plugin in your Appian environment to the latest version, download the bundle for that new version, and then ask Claude to verify that everything is in order. I have a skill in Claude that handles this task, and it works well for me.

    alvarog549347
    New Participant
    Nov 6, 2026 11:18 AM UTC

    Hi Raul,

    It turns out that during the version update—we’re not sure why—the platform configuration was changed, and for the plugin it now appears as follows:
    Feature Toggle:   ae.dev-copilot-api.lcp-api-plugin = false
    We’ve asked support to change it to true (in other environments, it’s set to true and works fine) to see if that resolves the issue.
    Just in case others are experiencing the same problem.

      Terms & ConditionsAccessibility statement