WCS with AI assistance¶
Overview¶
Since build 5.3.471 WCS is bundled with MCP server. This allows to easily integrate WCS with AI (Claude for example), and use AI assistance to configure and support WCS.
MCP server is installing and starting by default with WCS on the same host. But, of course, it may need some configuration before using in production.
Configuration¶
WCS configuration¶
The following minimal settings in /user/local/FlashphonerWebCallServer/conf/flashphoner.properties file enable WCS interaction with MCP server
oauth_auth_server_enabled=true
oauth_auth_server_issuer=http://localhost:9999
oauth_auth_server_ssl=false
MCP server uses WCS REST API v3 with OAuth authentication to interact with WCS. The settings above enable WCS internal OAuth service on port 9999, using HTTP by default.
MCP server configuration¶
The MCP server is installed to the /opt/wcs-mcp-ctl folder by default. It is started automatically with WCS if internal OAuth service is enabled. The YAML configuration files are in /opt/wcs-mcp-ctl/conf folder, the log files to check if something went wrong are in /opt/wcs-mcp-ctl/logs folder.
By default, MCP server listens port 6543 (as defined in /opt/wcs-mcp-ctl/conf/app.yaml)
server:
port: 6543
servlet:
context-path: /
# ssl:
# enabled: true
# certificate: "file:/path/to/crt.crt"
# certificate-private-key: "file:/path/to/privatekey.key"
WCS interaction is set up in /opt/wcs-mcp-ctl/conf/target-wcs.yaml
# Base URL of the WCS REST API that the MCP tools call.
wcs:
base: http://localhost:8081
# OAuth2 authorization server used to validate bearer tokens on incoming
# MCP requests.
mcp:
oauth:
authorization-server: http://localhost:9999
Connecting AI to WCS¶
The Claude is a good example to integrate with WCS. Suppose Claude CLI is installed on the same host:
Then start Claude and run /mcp
WCS needs authentication, choose it
Authenticate it
After that, Claude is ready to work with WCS. Please ask for example
and Clade will show them with detailed description.