Skip to main content
Brainy
September 8, 2026
Question

Facing issue while accessing Expression Rule using MCP Server

  • September 8, 2026
  • 11 replies
  • 91 views

Hi Everyone,

I am facing an issue while trying to access an Expression Rule through the MCP Server.

I have completed the following steps:

  • Created an Expression Rule.
  • Created a Service Account.
  • Created an MCP Server User Group.
  • Added the Service Account to the MCP Server User Group.
  • Granted View access to the MCP Server User Group for the Expression Rule.
  • Successfully connected to the MCP Server using the MCP Inspector tool.
  • Enabled MCP and Tools from Admin panel

However, when I try to access the Expression Rule through the MCP Server, I receive the following error:

Error: 500 - Internal Server Error

Could someone please suggest what might be missing or if there are any additional permissions/configurations required to access an Expression Rule through the MCP Server?

Any suggestions or input would be highly appreciated.

Thanks in advance!

11 replies

stefanhelzle0001
Brainy
September 8, 2026

Did you check any log files for details?

What is this expression doing? I fit uses other objects, make sure to check access for the service account to these other objects.

mathieud0001
Brainy
September 8, 2026

How are you testing the connection to the MCP exactly?

Also are you using the API Key to authenticate?

yogip3177Author
Brainy
September 8, 2026

@stefanhelzle0001, ​@mathieud0001 Thanks for your quick reply.

  • My Expression Rule is very simple—it only returns a hard-coded string, "Holla".
  • The MCP Server User Group has View permission for the Expression Rule, and the Service Account is a member of this group.
  • The MCP client is also able to successfully connect to the Appian server. I can see the tools exposed by Appian in the MCP Inspector. However, the issue occurs when I try to invoke any of the tools.
  • I am getting a 500 - Internal Server Error when calling the tools. I also checked the Appian logs, and they show an authentication error.

 

Logs:

Could this be related to the Service Account authentication or some additional permission/configuration required for invoking the MCP tools?

Any suggestions on what I should check would be greatly appreciated.

stephane.kamga
Employee
September 8, 2026

That AuthorizationException looks more like a platform role issue than object security  worth checking whether the service account is actually assigned the Designer role, since Viewer on the rule alone isn't enough.

yogip3177Author
Brainy
September 8, 2026

@stephane.kamga Thanks a lot for the quick reply.

I tried adding the Service Account to the Designer role as well, but I am still getting the error.

However, after assigning the Designer role, the error seems to have changed. It now appears to be related to the Designer.

Could you please take a look and let me know if I am missing any additional configuration or permissions?

Thanks again for your help.

yogip3177Author
Brainy
September 9, 2026

Hello Everyone,

Has anyone successfully used the MCP Server functionality? Is it working for anyone else?

I would appreciate it if you could share experience or any insights you may have.

Thanks in advance for your help and valuable input.

Regards,

mathieud0001
Brainy
September 10, 2026

Would probably recommend opening a case with Appian Support at this point.

yogip3177Author
Brainy
September 10, 2026

@mathieud0001 Thanks for your suggestion. Yes, we can do that, but it will take some time.

Also, if ​@mathieud0001 ​@stefanhelzle0001 ​@stephane.kamga  can tag or share with anyone who can help in this would be great.

Regards,

naresht804249
Participating Frequently
September 10, 2026

Try

  • Go to Admin Console → Users.
  • Open the Service Account.
  • Assign it the Designer platform role.
  • Confirm it remains in the MCP Server User Group.
  • Verify that group has Viewer access to the Expression Rule and any dependent objects.
  • Reconnect MCP Inspector using the Service Account’s API key, then invoke the tool again.
Naresh
yogip3177Author
Brainy
September 14, 2026

@stefanhelzle0001 ​@mathieud0001  ​@stephane.kamga  ​@naresht804249 Thank you all for your inputs and suggestions.

The same changes are working as expected in the Test environment. I will investigate further and, if I find anything interesting or relevant, I will update it here.

Note: As suggested by ​@stephane.kamga and ​@naresht804249, the Designer role is required for the Service Account. I believe this requirement is missing from the Appian documentation.

Thanks & Regards,